TListbox behaviour under OpenSuse/Gnome

[Chris_h174]

I can't reproduce with the original example*; you might want to post the  tweaked one to let us see if something changed. In the meantime, test with the attached project and tell me if it also fails, can you?

Note, though, that while the search is in progress and until it can unequivocally select a unique item the OnSelectionChange event won't be fired; might that be what you're seeing? If so, there is nothing you can do: that's how the GTK2 widgetset works.



* Tested on Xubuntu 18.04 x86_64

Thanks for your time Lucamar
I can't get your example to link.  I've been getting "crtbeginS.o" & "crtendS.o" not found for ages but it's never actually prevented linking.
My changes were simply to add ItemIndex to the StatusBar readout and add a listbox line with more common leading characters.
Chris

[Chris_h174]

I can't reproduce with the original example*; you might want to post the  tweaked one to let us see if something changed. In the meantime, test with the attached project and tell me if it also fails, can you?

Note, though, that while the search is in progress and until it can unequivocally select a unique item the OnSelectionChange event won't be fired; might that be what you're seeing? If so, there is nothing you can do: that's how the GTK2 widgetset works.



* Tested on Xubuntu 18.04 x86_64

Thanks for your time Lucamar
I can't get your example to link.  I've been getting "crtbeginS.o" & "crtendS.o" not found for ages but it's never actually prevented linking.
My changes were simply to add ItemIndex to the StatusBar readout and add a listbox line with more common leading characters.
Chris

OK.  So I managed to get it to link by selecting "Release" in Project|Options...
It still misbehaves IMHO.  Screenshot below shows "Item th" typed and correct line highlighted but ItemIndex still on "Item two".  If I type an extra character (can be a <space>) it corrects itself.  It looks to me as if ItemIndex lags the highlight by one character.
Thanks
Chris

[jamie]

I am not a Linux expert but maybe you need to perform a UPDATE during the KeyDown cycle..?

ListBox.Update..

or Repaint...
etc

[Chris_h174]

I am not a Linux expert but maybe you need to perform a UPDATE during the KeyDown cycle..?

ListBox.Update..

or Repaint...
etc

I'm very wise but... This is the built-in behaviour under gtk2.  I'm not intercepting keydown.
Chris

[lucamar]

It's in fact the default behaviour in GTk. The widgetset uses a relatively small delay to cope with slow typists and in case you made a mistake and have to delete the latest char(s) before admiting (and searching for) the  string. When you type some (more) char it "knows" that the previous ones are probably correct, so it acknowledges all but the more recent.

You can see this in, for example, the file manager (Nautilus, Thunar, pcfman, ...): the corresponding file selection goes always a little behind your typing of the name.

[jamie]

Sounds like the gtk was designed for slow old timers !

[lucamar]

Sounds like the gtk was designed for slow old timers !

I know you say it tongue-in-cheek but ... not really; in this particular case it does it to avoid having to do a relatively costly operation (the search) repeatedly when it's not really needed.

Think, for example, of a list of image files from a camera: there might be thousands and all of them start with the same four characters, hundreds start with the same five or six, and so on. Delaying the (full) search until the user stops typing makes it much more responsive.

Note also that at any time you can press <enter> to tell the widgetset to update the widget so its not really that cumbersome (most of the times )

[Chris_h174]

Sounds like the gtk was designed for slow old timers !

I know you say it tongue-in-cheek but ... not really; in this particular case it does it to avoid having to do a relatively costly operation (the search) repeatedly when it's not really needed.

Think, for example, of a list of image files from a camera: there might be thousands and all of them start with the same four characters, hundreds start with the same five or six, and so on. Delaying the (full) search until the user stops typing makes it much more responsive.

Note also that at any time you can press <enter> to tell the widgetset to update the widget so its not really that cumbersome (most of the times )

But I AM a slow old-timer.
I think the reasoning is flawed.  If it needs to behave like that then the highlight should too.  It is indicating to the user that they have selected an item when they have actually selected a different one!  In fact it doesn't always have to do an entire search, it only has to compare with the currently selected one and re-search if it differs.
Chris