-
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
Draft
maxpatiiuk
wants to merge
10
commits into
production
Choose a base branch
from
keyboard-shortcuts
base: production
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
maxpatiiuk
changed the title
Keyboard shortcuts
feat(KeyboardShortcuts): add customizable shortcuts for common actions
Jul 14, 2024
8 tasks
maxpatiiuk
force-pushed
the
keyboard-shortcuts
branch
from
July 14, 2024 02:37
d19d3ec
to
d3623a8
Compare
"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
maxpatiiuk
force-pushed
the
keyboard-shortcuts
branch
from
July 21, 2024 21:47
d3623a8
to
aa3beed
Compare
CSIRO mentioned users are having repetitive strain injuries due to this not being implemented |
Bugs:
|
maxpatiiuk
added a commit
to maxpatiiuk/calendar-plus
that referenced
this pull request
Dec 22, 2024
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
maxpatiiuk
added a commit
to maxpatiiuk/calendar-plus
that referenced
this pull request
Dec 23, 2024
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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)