> > This is also a questionable decision for a keyboard shortcut edit > actually. Quite often, shortcut editors would terminate the shortcut after > you entered it or with return if they do not want to allow that shortcut. I > have actually never seen a shortcut edit which terminates by some > artificial time. Frankly, once you type in a shortcut, it is clear that you > want that. No need to wait. And even if you had to wait, there should be a > backdoor not to annoyingly wait, like return. > > This is why I am claiming that this is retrofitting, not a clean solution. > > The bottom line: the ideal and current shortcut editor behaviour in most > apps that I have seen is not based on a timer. So, even if we add a > property, the timer still gets in the ideal way, although it will be better > than what we have now. It will not still be ideal though. >
This could probably be mitigated by disabling the timer when the maxKeyCount equals to one. I think that would be a fair decision to make.
_______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
