-
Notifications
You must be signed in to change notification settings - Fork 36
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
feat(KeyboardShortcuts): add customizable shortcuts for common actions #5097
base: production
Are you sure you want to change the base?
Conversation
d19d3ec
to
d3623a8
Compare
d3623a8
to
aa3beed
Compare
CSIRO mentioned users are having repetitive strain injuries due to this not being implemented |
Bugs:
|
The original keyboard shortcuts handling code was used as a basis for specify/specify7#5097, but then, on that PR I made logic more robust and added features. Now backporting the code from that PR back into calendar-plus. Fixes #255
The original keyboard shortcuts handling code was used as a basis for specify/specify7#5097, but then, on that PR I made logic more robust and added features. Now backporting the code from that PR back into calendar-plus. Fixes #255
"Keyboard" is a bit too generic/ambiguous
- Replace "show nodes with children only" checkbox with a toggle button. Reasons: - The checkbox was the only thing below the tree viewer - occupying an entire line of horizontal space. - Because of how Tab and Shift+Tab keys are used in the tree viewer, moving focus to elements below the tree viewer is not possible - you can only move above the tree viewer. That made this checkbox inaccessible from keyboard - The label for this checkbox is long, adding visual noise - it's cleaner as a small tidy button - Don't display split view controls if split view is not enabled to reduce visual clutter
aa3beed
to
f0f64b7
Compare
Added ability to set shortcut to any URL: out.mp4Use cases:
By default, I only included keyboard shortcut to open the keyboard shortcut viewer, and will add shortcut to go to the home page. For the rest, we can let people set those to what makes sense to them (I avoided setting too many be default as things can conflict with os/browser/browser extensions, unless we go for 3-4 key shortcuts) TODO:
|
Fixes #1746
Checklist
and self-explanatory (or properly documented)
Testing instructions
Keyboard Shortcuts
item to User tools - verify it looks goodKeyboard Shortcuts
page that has a default value assigned, make sure that the default keyboard shortcuts we have set do not already have an action assigned to them (we don't want to overwrite default browser or OS actions, unless we really have to, or unless user would expect us to do so)