SiComponents Forums

Have you assigned and translated the action for each top-level item?

Of course this depends on each developer opinion. And in case you want to prevent expert from replacing the resourcestrings you can always enclose resourcestrings section with {TSI:IGNORE ON} and {TSI: IGNORE OFF} tags. But be aware that translating resource strings is much slower when translating u...

Just use {TSI:IGNORE} tag to ignore single line with strings and {TSI:IGNORE ON} / {TSI:IGNORE OFF} to ignore block of lines. This will prevent expert from translating strings from this blocks. Also it would be helpful for you to download User's Guide from our download page and you will find there a...

The demonstrated source code snippet has used strings placed in const section not resourcestrings section. And the answer to modify project compiler settings to allow to use Asignable Typed Constants is absolutely correct.

May be setting Scaled property of form to False will solve this issue. Then your forms will look similar independing on screen fonts setings.

Unfortunately, there is no easy way to do this. But may be you can hack this by writing something like this in OnShow event of for example siFindDialog: procedure TForm1.siFindDialog1Show(Sender: TObject); var hnd: THandle; R: TRect; begin if (siFindDialog1.siLang = nil) or (siFindDialog1.siLang.Lan...

Just add TsiLang_CB6.BPI to the required packages list of your package and re-build your package. This should fix your problem.

Just check the ExtendedTranslations property of TsiLang. TLabeledEdit.Caption will be listed there.

This looks like there are left some OLD DCU files on your drive from previous version and BCB5 doesn't detect that it needs to re-compile new PAS files. So just delete all DCU, HPP and OBJ files from TsiLang folder and re-build the package.

We're searching the way to implement this. Hope this functionality will be available.

Both Delphi standard PrintDialog and TsiLang's siPrintDialog raise exception: "There is no default printer currently selected". And both fail to execute. So this is behavior (wrong or not I'm not sure) of Delphi's dialog. TsiLang's dialog doesn't introduces anything new in functionality it...

Yes, you should set the correct NumOfLanguages and LangNames in TsiLangDispatcher in case it is used in your project. Because dispatcher propagates these properties to all TsiLangs linked to it. TsiLang Expert can set the default number of languages and their name only for TsiLang and its descendant...

Unfortunately, we cannot reproduce such behavior on our side. This looks like something is wrong on your side. May be some thirdparty packages installed or something else.

What version of TsiLang Components Suite do you use? Have you tried to delete all DCU files and make "build all" to be sure that you use correct sources?

Web site and graphics for RegKeeper as well as all our products are designed by our company.