The new version fixed the problem. Thanks.isiticov wrote:But Style won't be published any case because TsiLangCombo always use OwnerDrawVariable style.
Search found 52 matches
- Fri Jun 24, 2005 1:31 pm
- Forum: TsiLang Components Suite
- Topic: Style property missing in TsiLangCombo 6.0
- Replies: 4
- Views: 5768
- Fri Jun 24, 2005 12:30 pm
- Forum: TsiLang Components Suite
- Topic: Style property missing in TsiLangCombo 6.0
- Replies: 4
- Views: 5768
- Fri Jun 24, 2005 11:59 am
- Forum: TsiLang Components Suite
- Topic: Style property missing in TsiLangCombo 6.0
- Replies: 4
- Views: 5768
Style property missing in TsiLangCombo 6.0
Hi, It seems that the Style property has not been published in TsiLangCombo 6.0. So the DropDownCount property has become useless and I'm limited to a single line display of the language items. This is not what I want: I want all languages to be visible (within the limits set by DropDownCount). Did ...
- Sun Mar 06, 2005 6:48 pm
- Forum: TsiLang Components Suite
- Topic: Problem with hints in toolbar
- Replies: 2
- Views: 4719
Re: Problem with hints in toolbar
Forget this question. My mistake, sorry.
- Sun Mar 06, 2005 6:12 pm
- Forum: TsiLang Components Suite
- Topic: Problem with hints in toolbar
- Replies: 2
- Views: 4719
Re: Problem with hints in toolbar
I should have mentioned that the TToolButtons appear in the Other section of the translation editor, but there, I only see the HelpKeyword property, not the Hint property.
- Sun Mar 06, 2005 6:01 pm
- Forum: TsiLang Components Suite
- Topic: Problem with hints in toolbar
- Replies: 2
- Views: 4719
Problem with hints in toolbar
Hi, I have a TToolbar with some TToolButtons. The buttons that are not connected to an action appear in the Hints section of the translation editor. That's fine. But all the TToolButtons that have a non empty Action property (most of them) do not appear there and I can't translate the hints. Any clu...
- Sun Feb 20, 2005 4:24 pm
- Forum: TsiLang Components Suite
- Topic: Translation editor autosave?
- Replies: 5
- Views: 6709
It is not so easy to revert the changes after the editor closed. How do you see the Autosave functionality will work? Did you have in mind automatically save on exit any without prompt? Then how to revert? Hi Igor, I see the feature as follows (roughly): 1. The editor window should get a new button...
- Sun Feb 20, 2005 9:25 am
- Forum: TsiLang Components Suite
- Topic: Translation editor autosave?
- Replies: 5
- Views: 6709
Re: Translation editor autosave?
[quote="isiticov]Yes, this is as designed, saving to DFM is performed on exit of editor if user accepts changes made.[/quote]
Then I vote for an Autosave option. Since it's so easy to revert a change , I think most users would appreciate such a feature.
Cheers.
Then I vote for an Autosave option. Since it's so easy to revert a change , I think most users would appreciate such a feature.
Cheers.
- Sat Feb 19, 2005 5:02 pm
- Forum: TsiLang Components Suite
- Topic: Translation editor autosave?
- Replies: 5
- Views: 6709
Translation editor autosave?
Hi, There's something I don't understand in the Translation editor. After I have made some changes, I'd like to exit that window, and if I click on save, I'm prompted to save into a SIL file. However, I want to save into the form data not into a SIL files. But there's no command to do that. So I hav...
- Sat Feb 19, 2005 8:52 am
- Forum: TsiLang Components Suite
- Topic: Repositioning components bug #1
- Replies: 2
- Views: 5542
Re: Repositioning components bug #1
Is there any reason why we can't just reposition components and have the whole thing done autmatically? I fully support this request. The editor should automatically assign the current property values to each language. Otherwise, this is a two-pass process. First, you have to manually copy all the ...
- Thu Feb 17, 2005 2:38 pm
- Forum: TsiLang Components Suite
- Topic: Compilation problem after CONST translation
- Replies: 2
- Views: 4841
If we would move automatically strings from declration places this may cause a lot of problem for all of us. Adding {$J+} compiler directive at the beginning of the unit Correct. Actually, it is just necessary to bracket the modified declarations with a {J+} / {J-} pair, which could be done automat...
- Thu Feb 17, 2005 1:47 pm
- Forum: TsiLang Components Suite
- Topic: Compilation problem after CONST translation
- Replies: 2
- Views: 4841
Compilation problem after CONST translation
Hi again, Sorry but I have another one to report. I have a unit A with no form containing a big CONST section. Only a part of the strings declared there have to be translated. So I deleted the non translatable strings in the editor and generated the code from TsiLang Expert. Since the unit has no fo...
- Thu Feb 17, 2005 11:07 am
- Forum: TsiLang Components Suite
- Topic: Another minor quirk with CONST translation
- Replies: 3
- Views: 5155
- Thu Feb 17, 2005 9:42 am
- Forum: TsiLang Components Suite
- Topic: Another minor quirk with CONST translation
- Replies: 3
- Views: 5155
Another minor quirk with CONST translation
Hi again, I have noticed that if the CONST string has a leading CRLF sequence, like this: #13#10#13#10'My const' the leading CR/LF characters are removed by TsiLang expert when generating the translation code. This is a minor problem since you can restore them in the editor, however , you might easi...
- Thu Feb 17, 2005 9:10 am
- Forum: TsiLang Components Suite
- Topic: Problem with CONST strings
- Replies: 1
- Views: 4026
Problem with CONST strings
Hi,
It seems that TsiLang has a problem with such declarations:
const
psMyConst : PChar = 'MyText';
In that case, TsiLan expert says:
StringID : strPChar
String Constant : PChar
Will be replaced by: siLanf.GettextOrDefault('strPChar')
Regards.
It seems that TsiLang has a problem with such declarations:
const
psMyConst : PChar = 'MyText';
In that case, TsiLan expert says:
StringID : strPChar
String Constant : PChar
Will be replaced by: siLanf.GettextOrDefault('strPChar')
Regards.