|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Strange problem using Delphi and VCL library
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Strange problem using Delphi and VCL library
|
| Moderated by: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius |
|
||||||||||||||||
| Strange problem using Delphi and VCL library - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
salvatore28 Language Partners 
|
hello all, after a long time I removed the dust from Delphi (Tokyo 10.2.3) and I'm writing a little program. I have also included the Sisulizer VCL libraries for the language dialog and language change at run-time. The program uses also the JVCL library to store settings and main form position and state into an XML file. The strange problem occurs when the main form is maximized and I change the language using the dialog:
Thank you. Salvatore Last edited on Sun Nov 11th, 2018 05:30 pm by salvatore28 |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator 
|
Sounds like it "localizes" the properties of JVCL. You might want to exclude these window position properties from localization. The libraries enumerate all properties at run-time and localizes them in memory. It already knows many exceptions - but might not be aware of JVCL. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
salvatore28 Language Partners
|
hello Markus, nice to read you after some time  I want to add to the problem that I have localized only the strings of my program, and that I have left all the others untranslated, JVCL included; this means that the native JVCL strings are used when language changes, in fact using the original untranslated JVCL strings. So, in theory, none of the JVCL properties should be "localized". Add-on: But size and state should never be localized, for any component. Or am I wrong? What do you think? Salvatore Last edited on Mon Nov 12th, 2018 09:43 am by salvatore28 |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
A language change at runtime is not part of the official VCL logic. It has to overcome some limitations and is pretty tricky. There must be some loop enumerating the controls in the Delphi code coming with Sisulizer. You might need to exclude the property there. But I'm not a Delphi developers as you know. So I'm not of much help here. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
salvatore28 Language Partners
|
so, do you mean that I should exclude those properties in my code, not in the Sisulizer IDE? Thank you Salvatore Last edited on Mon Nov 12th, 2018 08:49 pm by salvatore28 |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Yes. I expect this is the fastest approach to overcome that behaviour. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
salvatore28 Language Partners
|
ok, I'll try. Salvatore Last edited on Tue Nov 13th, 2018 08:38 am by salvatore28 |
||||||||||||||||
| |||||||||||||||||
| Current time is 10:11 am | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Strange problem using Delphi and VCL library | |
Sisulizer software localization tool - Three simple steps to localize
