Review Request: Change default shortcuts for Previous and Next visited contexts to Alt+Left and Alt+Right
David Nolden
david.nolden.kde at art-master.de
Sun Jun 19 19:47:03 UTC 2011
> On June 18, 2011, 11:43 a.m., David Nolden wrote:
> > These very frequent and useful actions need very handy shortcuts. I picked Meta when creating them, because most other such handy shortcuts were already blocked by something else (KDE3 days). ALT+Direction is already blocked implicitly too: You can use ALT+Dir to navigate within the navigation-tooltip, or within the open context browser, so these shortcuts unfortunately won't work.
>
> Olivier Jean de Gaalon wrote:
> This'll take some rethinking then, since the meta shortcuts aren't ideal (and don't work under Unity).
> Especially if we end up with a browser-like interface, the Alt+Left/Right for prev/next will IMO take precedence. Is there any way we can change the context browser shortcuts?
>
> David Nolden wrote:
> The navigation within the context-browser should be some MODIFIER+Direction, and there's no other modifier except for ALT which can fulfil this, especially considering that the META modifier will be blocked by the window-manager in future. CTRL and SHIFT already have too many uses right within the editor.
>
> ALT+Shift might be a candidate for the history navigation.
>
> Niko Sams wrote:
> I use the previous context action regularly. Having the same shortcut as in the Browser would absolutely make sense - an additional modifier would make it harder to use. (Besides the fact that Alt+Shift+Left/Right is already taken by prev/next tab).
>
> I however see the context-browser modifier, and have no solution for that clash. Personally I never use it - I always use the mouse for that.
>
> Milian Wolff wrote:
> I'm with both of you groups. But can we not use QAction's contexting to make the ALT+Dir browsing in tooltip take precedence? After all, you don't want to jump history when you look at the tooltip. Since that one is only shown after a short delay I think this would be an acceptable compromise?
@Milian: No, because the context-browser toolview is affected too, and that one may be permanently visible.
Also, the navigation-widgets can appear in many different places: As popups, in the context-browser, embedded in quickopen, embedded in code-comletion, and the flow of input is different for each case, so changes here are hard to do.
Anyway there are enough alternative shortcuts available: What about ALT+PGup and ALT+PGdown? While consistency with other applications is nice, internal consistency is nicer, so the solution is to simply find good alternative shortcuts. Btw. Meta+Left and Meta+Right _are_ nice shortcuts imo.
- David
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/101600/#review3996
-----------------------------------------------------------
On June 15, 2011, 5:21 a.m., Olivier Jean de Gaalon wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/101600/
> -----------------------------------------------------------
>
> (Updated June 15, 2011, 5:21 a.m.)
>
>
> Review request for KDevelop.
>
>
> Summary
> -------
>
> As summary
>
>
> Diffs
> -----
>
> plugins/contextbrowser/contextbrowser.cpp 86cd7f9
>
> Diff: http://git.reviewboard.kde.org/r/101600/diff
>
>
> Testing
> -------
>
>
> Thanks,
>
> Olivier Jean de
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20110619/edf0517a/attachment.html>
More information about the KDevelop-devel
mailing list