That's interesting, i also had tried that Key:= 0, limited by conditions, too but didn't like it either
(but mostly because with this reactice correction the positive reason-why would be still unidentified.
But i had no idea yet where to search in the hierarchy. Presumingly item- resp. selected- index is set or preinitialized with zero somewhere)
I tried the widgetset change and it does suppress the jump-to-beginning, but i don't understand yet how it works regarding the conditions
(in combination with Shift, Ctrl, .. a char is allowed).
Currently i encounter the following caveat:
- "builtin"-keystrokes resp. common combination like Ctrl-a, Ctrl-x .... do still work
- user defined keystrokes like eg. Ctrl-s are broken (i mean, if i define on app level that when pressing Ctrl and "s" on an item, something specific should be done, it won't work now)
I'm a bit unsure about this difference. Shouldn't all combinations with Shift, Ctrl, .. and char passed through?