-
Notifications
You must be signed in to change notification settings - Fork 0
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
Make navigational shortcuts visible #39
Comments
In detail view we can add to In the main view we should probably refactor |
We already handled Escape to close the process details, but now we tell the user that in case they’re confused. A cool side effect of refactoring the controls to be derived from props is that the stop/start toggle’s label will update to show which one is selected. Refs #39.
I'm not sure I feel super strongly about documenting double-clicking / pressing Enter, I feel like that's pretty obvious as the central action of the app / something that someone would pick up from the README? (And if we were to document that, should we document using the arrow keys and typeahead search too?) But the process table could easily add such shortcuts using the new command menu and command set APIs introduced in #72. We might need to alter how the menu displays the command descriptions since these commands wouldn't have single-key triggers, but that'd be minor. We can revisit before the 1.0. |
The text was updated successfully, but these errors were encountered: