Slickedit textmode keybinding F10 missing... #SE2019

[jbezem]

Yes, I'm older, I remember SlickEdit from before Visual SlickEdit, I know what MicroEdge was.
AND I still use the SlickEdit text-mode key-bindings.
Now, since several versions I have gotten used to the fact that the F10 function key has been given a binding 'debug-step-over'. OK, so in each fresh install on a new machine (at least) I know to unbind the key, and then my 'find' command was reachable with my combination "F10-s-f".
For SE2019 it looked again the same, only, after unbinding, it still doesn't work! It now says 'key not defined'.
Can someone help me? 25+ years of muscle memory is hard to re-train.

Thanks, Johan

[Graeme]

Hi Johan
Maybe the discussion we had about it last time will help until there's a solution
https://community.slickedit.com/index.php/topic,8425.msg35963.html#msg35963

[jbezem]

Hi Graeme, I had all but forgotten about your solution - and even about having the problem in the first place... It's been a long time, and I've mostly done project management iso. programming much. I've even skipped a few SE versions. But it would still be good to see it fixed again, the muscle memory is still there. And your solution still works (-around)! +1

[Clark]

This seems to a problem with Qt5. We will look into this.

[Clark]

Fixed for 24.0.1. No release date set for this yet. Should be before end of year.

[jbezem]

Many thanks!