Support forum of the software localization tool Sisulizer


.NET, Delphi, ... - Sisulizer Localization Tool Support Home

Get in contact with the makers of Sisulizer.
Our forum is open for all questions around Sisulizer from customers and prospects.
Don't hesitate to register and ask. The Sisulizer team will answer ASAP.
Search     Help Home Sisulizer Website Download
Search by username
Not logged in - Login | Register 
.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
New Topic Reply Printer Friendly
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
AuthorPost
 Posted: Sun Nov 11th, 2018 06:27 pm
PM Private Upload Quote Reply
salvatore28
Language Partners


Joined: Sun May 4th, 2008
Location: Reggio Emilia, Italy
Posts: 157
Status: 
Offline
 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:
  • The main form returns to its unmaximized state
  • The main form travels to the upper left corner of the screen
  • The maximize icon of the main form doesn't reflect this change and still shows as maximized
  • If I drag the main form the maximize icon returns to the correct aspect
Do you have any idea about what could be the problem? Does the Sisulizer VCL library change anything in the window size and state?

Thank you.

Salvatore

Last edited on Sun Nov 11th, 2018 06:30 pm by salvatore28
Back To Top PM Private Upload Quote Reply

 Posted: Mon Nov 12th, 2018 08:59 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3195
Status: 
Offline
 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
Back To Top PM Private Upload Quote Reply

 Posted: Mon Nov 12th, 2018 10:36 am
PM Private Upload Quote Reply
salvatore28
Language Partners


Joined: Sun May 4th, 2008
Location: Reggio Emilia, Italy
Posts: 157
Status: 
Offline
 hello Markus,

nice to read you after some time :q

 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 10:43 am by salvatore28
Back To Top PM Private Upload Quote Reply

 Posted: Mon Nov 12th, 2018 11:55 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3195
Status: 
Offline
 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
Back To Top PM Private Upload Quote Reply

 Posted: Mon Nov 12th, 2018 09:49 pm
PM Private Upload Quote Reply
salvatore28
Language Partners


Joined: Sun May 4th, 2008
Location: Reggio Emilia, Italy
Posts: 157
Status: 
Offline
 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 09:49 pm by salvatore28
Back To Top PM Private Upload Quote Reply

 Posted: Tue Nov 13th, 2018 03:16 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3195
Status: 
Offline
 Yes. I expect this is the fastest approach to overcome that behaviour.

Markus



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Tue Nov 13th, 2018 09:37 am
PM Private Upload Quote Reply
salvatore28
Language Partners


Joined: Sun May 4th, 2008
Location: Reggio Emilia, Italy
Posts: 157
Status: 
Offline
 ok, I'll try.

Salvatore

Last edited on Tue Nov 13th, 2018 09:38 am by salvatore28
Back To Top PM Private Upload Quote Reply

Current time is 01:46 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



WowUltra modified by Sisulizer Copyright © 2007-18 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Impress - Privacy statement

Sisulizer software localization tool - Three simple steps to localize