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

Keyboard navigation in message & callstack views in the Editor window #11

Open
Kalmalyzer opened this issue Feb 17, 2017 · 0 comments
Open

Comments

@Kalmalyzer
Copy link
Contributor

Kalmalyzer commented Feb 17, 2017

It is possible to click in the Editor's Uber Console window and mark individual messages, but there is no keyboard navigation (up-arrow/down-arrow, page up/down, home/end). I miss this a lot.

If we were to combine this with the filter window then I think the following design could work. What do you think? Suggestions welcome!

There are three views which are keyboard controllable -- the search filter input field, the list of messages, and the list of stackframes. The user should be able to switch focus (and keyboard input) between the three.

Visual representation of selection
For the filter view, there are just two styles -- active (this is when you can edit the filter string) and inactive.

For the message and stack frame views, elements can have one out of three visual presentations: not selected (today's grey), selected-but-inactive (a new, different grey), and selected-and-active (today's blue). Clicking on an entry in the message or stack frame view will move focus to that view and select the entry that was clicked on. Clicking on an entry in the other view will make the selected entry in the first view display as selected-but-inactive mode.

Keyboard navigation will change which entry in the view is currently selected; the view will scroll as needed to ensure that the entire entry is visible (or if the entry is higher than the view, the top portion of the entry should be visible).

Keyboard bindings
It should ideally be possible to navigate between the three views using the keyboard (tab + shift-tab?).

Pressing Return on a message could be used to open source file externally.

Single-clicking on an entry in the callstack view has no effect; there is double-clicking to open file externally and right-clicking to show/hide nearby code. These operations could map to space (for hiding/showing nearby code) and Return (for opening file externally).

@Kalmalyzer Kalmalyzer changed the title Keyboard navigation in message window & callstack window Keyboard navigation in message window & callstack views in the Editor window Oct 30, 2017
@Kalmalyzer Kalmalyzer changed the title Keyboard navigation in message window & callstack views in the Editor window Keyboard navigation in message & callstack views in the Editor window Oct 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant