Changes done in Delphi are lost!
Posted: Mon Mar 02, 2009 9:31 pm
On our applications, if we change, in Delphi, the Caption of a component, without making any change into TranslationEditor, the modification is lost 
After saving the form, a look into the DFM file show that the Caption change has been recorded into the Delphi part of the file, but not in the TsiLang encrypted translation list (as proven with a VSS comparison).
The modification is lost even if we open TranslationEditor to ensure that TsiLang has seen the change to that component. The TranslationEditor effectively show the new value, but even then, saving the form does not record the TsiLang translation list.
However, if we click into any cell of the TranslationEditor, then TsiLang Core remembers that the form has some modification to record and then the Caption change is recorded and restored on next opening.
I suspect that in some situation, TsiLang Core does not raise its "dirty flag" to remember that some change had occured. By clicking into any cell, the flag is raised and everything goes well after that...
N.B. That problem was observed with version 6.3.1 and upgrading to version 6.4 does not correct the problem.
After saving the form, a look into the DFM file show that the Caption change has been recorded into the Delphi part of the file, but not in the TsiLang encrypted translation list (as proven with a VSS comparison).
The modification is lost even if we open TranslationEditor to ensure that TsiLang has seen the change to that component. The TranslationEditor effectively show the new value, but even then, saving the form does not record the TsiLang translation list.
However, if we click into any cell of the TranslationEditor, then TsiLang Core remembers that the form has some modification to record and then the Caption change is recorded and restored on next opening.
I suspect that in some situation, TsiLang Core does not raise its "dirty flag" to remember that some change had occured. By clicking into any cell, the flag is raised and everything goes well after that...
N.B. That problem was observed with version 6.3.1 and upgrading to version 6.4 does not correct the problem.