On Mittwoch, 9. April 2014 16:39:53 CEST, Jan Kundrát wrote:
Hi,
Thomas, others, is there any reason why we don't have a couple
of QActions for stuff like "go to next message" (key down),
"previous one" (key up), "scroll message down" (space), "scroll
message up" (backspace)?
Afair the itemviews implements the handling in the keypress event, not the
shortcut event.
So it will likely be required to re-reimplement that (and cloning parts of it
as reaction to the action slot)
One would set the action context to Qt::WidgetShortcut or
Qt::WidgetWithChildrenShortcut and the actions need to connect some
moveCursor() calling slots.
Absent QKeySequence::StandardKey's should be no issue as the keys are hardcoded
anyway (so far)
An obstacle could become the complex selection thing (ctr/shift)
It should be doable (for custom QTreeView etc.), but it's not like: "let's just bind
these slots to some other action"
(Scroll up/down by back/space is of course no problem - internal feature
already anyway)
Cheers,
Thomas
