Forum > LCL

TListView.OnChange Event Firing Bug

(1/4) > >>

msintle:
Lazarus trunk affected, reproduces on macOS.

Previously:

When you select a new TListItem, TListView.OnChange fired with the deselected item first, and then with the selected item.

Currently:

TListView.OnChange fires with the newly selected item first, and then the deselected item.

This breaks a lot of code which assumes, based on historic behavior, that the old item is deselected first, and then the new item is selected (instead of doing it chronologically inaccurately).

Bart:
Please report n the bugtracker.
It would be helpfull if you can find the guilty revision (use 'git bisect' for that).

Do you know if this happens on Cocoa WS only, or also on e.g. Windows?

Bart

wp:
On Windows it first fires with "Selected= false", and then with "Selected=true".

Bart:
So, one should not rely on order but on Selected param?

Bart

msintle:

--- Quote from: wp on September 12, 2024, 11:43:58 am ---On Windows it first fires with "Selected= false", and then with "Selected=true".

--- End quote ---

So the issue seems isolated to macOS, and does not happen on Windows.

Navigation

[0] Message Index

[#] Next page