Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature ] Missing Hotkeys? Navigation between split-views ⌨️ #5507

Closed
martinandersen3d opened this issue Apr 23, 2020 · 2 comments
Closed
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@martinandersen3d
Copy link

martinandersen3d commented Apr 23, 2020

Description of the new feature/enhancement

There are nice hotkeys to split view

{ "command": "splitVertical", "keys": ["alt+shift+v"] },
{ "command": "splitHorizontal", "keys": ["alt+shift+h"] },

Feature:
After a split, we need a way to toggle or switch between the two splits. Currently the "next tab" hotkey does not work. I have not found a way to tab/navigate between two split-views.

Suggestion: Add hotkeys to tab between a split view

Proposed technical implementation details (optional)

{ "command": "focusNextSplitview", "keys": ["alt+shift+n"] }
{ "command": "focusPrevSplitview", "keys": ["alt+shift+p"] }

Maybe later:

{ "command": "focusSplitview1", "keys": ["alt+shift+1"] }
{ "command": "focusSplitview2", "keys": ["alt+shift+2"] }
{ "command": "focusSplitview3", "keys": ["alt+shift+3"] }

maybe and option to just use the ctrl+tab.. and cycle through splits and "tabs" with the same hotkey..

Suggestions for better naming is very welcome, maybe some more consistent with other names in the application? And maybe also hotkeys suggestions..

@martinandersen3d martinandersen3d added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Apr 23, 2020
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Apr 23, 2020
@zadjii-msft
Copy link
Member

So there are already the following to move focus in a particular direction:

{ "command": { "action": "moveFocus", "direction": "down" }, "keys": "alt+down" },
{ "command": { "action": "moveFocus", "direction": "left" }, "keys": "alt+left" },
{ "command": { "action": "moveFocus", "direction": "right" }, "keys": "alt+right" },
{ "command": { "action": "moveFocus", "direction": "up" }, "keys": "alt+up" },

and there's #2871 for nextPane and prevPane keybindings. I'm gonna resolve this issue as a dupe of that thread for now - let me know if that's not what you were looking for.

/dup #2871

@ghost
Copy link

ghost commented Apr 23, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Apr 23, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Apr 23, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants