Forum > Lazarus

Lazarus Release 2.2.4

(1/6) > >>

The Lazarus team is glad to announce the release of Lazarus 2.2.4.

This is a bugfix release and was built with FPC 3.2.2.

Here is the list of changes for Lazarus and Free Pascal:

Here is the list of fixes for Lazarus 2.2.x:

The release is available for download on SourceForge:

Choose your CPU, OS, distro and then the "Lazarus 2.2.4" directory.

Checksums for the SourceForge files:

Minimum requirements:

   2k, 32 or 64bit.

   gtk 2.24 for gtk2, qt4.5 for qt, qt5.6 for qt5, 32 or 64bit.

Mac OS X:
   Cocoa (64bit) 10.12, Carbon (32bit) 10.5 to 10.14, qt and  qt5 (32 or 64bit).

The gitlab page:

For people who are blocked by SF, the Lazarus releases from SourceForge are mirrored at:

Unfortunately at least this one is still missing:
LCL/TListView: More complete fix of issue #39708, based on patch by d7_2_laz...
... referring to this issue:
Windows, virtual listview, "Item" in "Edited" becomes to be wrong when selection changed during editing
--> What can we do for to make it work again with the 2.2.4?

Hmmm... This report is tagged with "milestone 2.4". If I remember correctly, this was some kind of difficult work with some changes deep in the heart of the listview, and I was not sure if we did not break something else.

Yes wp (thank you!).
There was also some keeping track of the selection list (around "InitMultiSelList", "UpdateMultiSelList" & co.; cannot see them within the 2.2.4) last april, maybe you remember roughly. I applied those patches as discussed last april (from lazgit), and what i can say is that upfrom these changes the virtual listview, multiselect, did work smart and without any problems regarding this bunch of issues discussed (it was a closed long story for me).
Will it be surely within a 2.4?  And how to have it for (on top of) the 2.2.4?


--- Quote from: d7_2_laz on September 28, 2022, 05:17:30 pm ---Will it be surely within a 2.4?  And how to have it for (on top of) the 2.2.4?

--- End quote ---
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?


[0] Message Index

[#] Next page

Go to full version