Will it be surely within a 2.4? And how to have it for (on top of) the 2.2.4?Well, 2.2.4 is done - nothing can change it any more. If you are sure that the committed fix is working and has no side-effects, we can target it for v2.2.6 (or 2.4 - whichever comes first). In the meantime it will be in "fixes" then. Is it only the commit that you cited above?
I confirm what RadDeveloper said is reproducible on Lazarus 2.2.2 Linux GTK2.
But that only happens on new project, so the steps to produce the issue are:
1. Start Lazarus
2. File > New > Project > Application > OK
3. Project > View Project Source
4. Close the project1.lpr tab on the Source Editor
5. Project > View Project Source
I can reproduce.Quote from: HandokoI confirm what RadDeveloper said is reproducible on Lazarus 2.2.2 Linux GTK2.
4. Close the project1.lpr tab on the Source Editor
Will it be surely within a 2.4? And how to have it for (on top of) the 2.2.4?I now made several attempts to merge the changes into the fixes branch. But since solution of these bugs has a long history there were commits that were not backported to main, some were reverted, and some were replaced by the changes that you mention, some were not. Therefore I think it is too risky to introduce other issues into the fixes branch, and I would like you to wait for the v2.4 release which will contain the current code automatically (for sure!) because it will be a snapshot of the main branch at the time when this version will be tagged.
I can confirm this issue with Qt and Qt5 under x11, so it's not gtk2 only problem - but this bug is reproducable only with newly created, unsaved project.
I notice a minor bug about TFrames that was already present in previous version (2.2.2).
When we put a frame on a form, the unit of the frame is not automatically inserted in the uses section by the IDE, that results in compile error. We have to do by hand.
@PascalDragon: no, I tried to do it but I can't create an account on GitLab, my email is rejected...
Did I do something wrong while updating? Or has anyone got the same problem?
So all you need to do (after you changed that path, and ignored the warning), is from the "tools" menu: "rebuild lazarus ..."
@PascalDragon: no, I tried to do it but I can't create an account on GitLab, my email is rejected...
This has nothing to do with ARM processors. Show us some code - compilable code -... Then you will get more reasonable answers.
Remove the close, because ShowMessage is not modal. That goes for every platform btw.
... because ShowMessage is not modal. That goes for every platform btw.
Which isn't the case on Linux/gtk2..Which makes both of us wrong.
You should create a feature request at https://gitlab.com/groups/freepascal.org/lazarus/-/issues