Reproduction step: 1. Configure shortcut for 'Quick Open Action'. 2. Use shortcut and validate an action (eg. Move To Next Line). 3. The action is ignored, 'Quick Open' is open. Expected: 3. The action is validated. Additional information: - Some actions are performed correctly (eg. Show folding Markers), but 'Quick Open' is still open. - Whether or not there is a shortcut to 'Quick Open' makes no difference. - This does not happen on Kate.
By "validating" an action, do you mean "triggering" it? While a Quick Open window is open and active? If so, I don't think this is much of a problem - just dismiss the Quick Open window first, e.g. by pressing the Escape key. As far as I know, KDevelop's and Kate's implementations of Quick Open are completely separate/unrelated (though maybe one was inspired by the other). So major differences between them are to be expected. KDevelop's Quick Open window is a QuickOpenWidget (inherits QMenu) inside a QDialog. QuickOpenWidget::eventFilter() overrides handling of many keyboard events. See kdevelop/plugins/quickopen/quickopenwidget.cpp.
> By "validating" an action, do you mean "triggering" it? Yes, with "Enter" key on the keyboard. > While a Quick Open window is open and active No. I focus on a document before doing “Quick Open Action” shortcut.
I guess you mean Help=>Find Action... shared by all KDE applications, not KDevelop's custom Quick Open Actions. Yes, that one is somewhat buggy in KDevelop. Even crashed once when I typed quickly while the CPU was busy compiling. Move to Next Line doesn't work, but Show Folding Markers works perfectly for me.
(In reply to Igor Kushnir from comment #3) > I guess you mean Help=>Find Action... Oh yes, I just saw that I named it wrong in my first post :/ > Move to Next Line doesn't work, but Show Folding Markers works perfectly for me. Without "Quick Open" opening? Because with me it's systematic. And for certain actions like "Move cursor to previous blank word" (js command added via KatePart), my focus switches to the rightmost split document after the command has been executed. It's a pity to have strange behavior or crashes, because it's much more practical than looking for an action in the menus.
(In reply to Jonathan Poelen from comment #4) > > Move to Next Line doesn't work, but Show Folding Markers works perfectly for me. > > Without "Quick Open" opening? Because with me it's systematic. Yes, I don't see any bugs with Show Folding Markers, whether I trigger this action via a custom shortcut or by pressing Enter in the Find Action... popup. > And for > certain actions like "Move cursor to previous blank word" (js command added > via KatePart), my focus switches to the rightmost split document after the > command has been executed. Maybe your custom assigned shortcuts overlap with other shortcuts or with the main menu shortcuts? (see also Bug 497660) > It's a pity to have strange behavior or crashes, because it's much more > practical than looking for an action in the menus. I think the crash I have encountered is not caused by bugs in KDevelop but rather in KF or Qt code. The strange behavior may be caused by custom handling of key presses in KDevelop, possibly implemented more than a decade ago...