Another related consequence of this bug fix is that labels read from v2.2.2-lfm files now have their ParentColor set to false. Reset this to true, and the Color line will be removed from the lfm after saving (because the Parent has color clDefault, too).
I don't see any size change in the test that I did before writing this post. In your diff a PageControl is mentioned. IIRC there is/was an issue with autosizing related to PageControls. I'd speculate that the width changes that you see are due to it.
Be guaranteed: Nobody makes changes in published properties just for fun. 100% backward compatibility cannot be assured, and in fact every fixed bug breaks backward compatibility.
Why not "Search & Replace" in an external editor? You cannot damage anything provided that you have a backup copy of the changed lfm file.Another related consequence of this bug fix is that labels read from v2.2.2-lfm files now have their ParentColor set to false. Reset this to true, and the Color line will be removed from the lfm after saving (because the Parent has color clDefault, too).
How can I do this? My .lfm file is huge, see attached. Is there a preferences option available or do I have to use a text editor on the .lfm file?
You provided only the lfm file which is read by the IDE only as text. Please add the correspondig pas file, too.I don't see any size change in the test that I did before writing this post. In your diff a PageControl is mentioned. IIRC there is/was an issue with autosizing related to PageControls. I'd speculate that the width changes that you see are due to it.
Maybe my .lfm file is then a good test. I attached it.
That was my question. So I have to use a text editor.How can I do this? My .lfm file is huge, see attached. Is there a preferences option available or do I have to use a text editor on the .lfm file?Why not "Search & Replace" in an external editor? You cannot damage anything provided that you have a backup copy of the changed lfm file.
I attached this now.Maybe my .lfm file is then a good test. I attached it.You provided only the lfm file which is read by the IDE only as text. Please add the corresponding pas file, too.
The lfm is a v2.3 file now so that I cannot see what changes when a v2.2.2 file is upgraded to v2.3I attached this now.Maybe my .lfm file is then a good test. I attached it.You provided only the lfm file which is read by the IDE only as text. Please add the corresponding pas file, too.
The lfm is a v2.3 file now so that I cannot see what changes when a v2.2.2 file is upgraded to v2.3This works for me still:
it is clear that each autosized checkbox has a different width in v2.3 than in v2.2.2.
I think the user should be informed. So then a lfm file from 2.2.x is loaded to 2.3.x, and a value in the .lfm file changes, he gets a nota that there are changes in the .fm file because of different auto-size calculation results.I doubt. Nobody reads the release notes, even you did not read the note about the label changes (I agree that the connection to your issue is not mentioned, it's more or less a side-effect of that fix, so be excused)... But anyway, I added a short note about the changes in TCheckbox/TRadioButton (https://wiki.freepascal.org/Lazarus_2.4.0_release_notes#TCheckbox.2C_TRadioButton).
This would have helped me because I made a change, wanted to commit this to my Git repo and saw more than 300 changes. I searched around, could not find anything and now I somehow stole your time to help me (sorry for that). I think others will face the same situation, therefore such an info will help the users but also the Lazarus developers to prevent reports.
What about my proposal with the Default Color?Report it to bugtracker. I won't touch this issue, though, maybe another developer will. But provide a simpler example, ideally just a form with a label. Your current form is too complex and the history of it is not known. Looking at your original v2.2.2 form of reply #2, for example, I see that all labels have ParentColor = false. How does it get there? Did you set it? Or is it a consequence of the linkage of ParentColor and Transparency in v2.2.2? Groupbox Channel1CB of your file has ParentColor= false when I load the file into Laz 2.2.2, but ParentColor is true when I load it into Laz main. Why? Due do another fix? Another issue? Or is it a side-effect of the same clDefault issue that is already fixed and documented in the link I gave above? This is a huge investigation with your sample file, I am afraid nobody will take the time...
And if you are thinking of a compiler message: Again, I doubt that anybody will find such a note among the myriads of hints and warnings that FPC spits out already today.No, I meant a MessageDlg. So you see a popup the first time your LFM is converted from 2.2 to 2.3. This should do the job well from my perspective.
No. MessageDlg will be as annoying as the exception dialogs that appear today when a form with an unknown property is read from the LFM.But that's the idea.
Your current form is too complex and the history of it is not known. Looking at your original v2.2.2 form of reply #2, for example, I see that all labels have ParentColor = false. How does it get there? Did you set it? Or is it a consequence of the linkage of ParentColor and Transparency in v2.2.2? Groupbox Channel1CB of your file has ParentColor= false when I load the file into Laz 2.2.2, but ParentColor is true when I load it into Laz main. Why? Due do another fix? Another issue? Or is it a side-effect of the same clDefault issue that is already fixed and documented in the link I gave above? This is a huge investigation with your sample file, I am afraid nobody will take the time...I see. I started with the form with Laz 2.0.x, with every new Laz version I encountered some additions to the .lfm file despite I never dealt with the color settings. Therefore I assume the settings are there because of Lazarus's changes.
take advantage of the anchoring method coming with Lazarus (https://wiki.freepascal.org/Autosize_/_Layout (https://wiki.freepascal.org/Autosize_/_Layout), https://wiki.freepascal.org/Anchor_Sides (https://wiki.freepascal.org/Anchor_Sides)).Yes, I discovered it a while ago and setup all my forms with it. Only the particular big form of this thread made problems and I gave up. I will give it now another try.
Yes, I discovered it a while ago and setup all my forms with it. Only the particular big form of this thread made problems and I gave up. I will give it now another try.