-
Notifications
You must be signed in to change notification settings - Fork 35
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]: New Shortcuts #1044
[feat]: New Shortcuts #1044
Conversation
center align, vishraams, larivar
@AkalUstat ji, I am unable to use the keyboard shortcuts. Testing it here Do I need to enable it from somewhere or something? |
You have to be clicked on the shabad viewer. Found that hukamnama, search, and ang have that component in common so that is where i put. I could put it higher up in the component tree if you like |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Keys not working as of now (which you have mostly fixed I think), and there's a blue outline on the viewer.
and errors with alt+e
@saintsoldierx I will create some user info for this stuff in a separate PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Awesome work @AkalUstat
I only have a concern about the keyboard shortcuts we use
For Shahmukhi transliteration toggle, we use: ctrl + alt + shift + t + s, that's five keys. It takes both hands to toggle that. It can be done with one hand as well, but all fingers are used and are put in a weird position.
Also, @AkalUstat are we using the same shortcut keys that are currently in desktop, if not, we should.
@saintsoldierx @maneetpaul @ManjotS veerjis, can any of you you review the shortcut keys used here if you haven't yet.
|
Found a small bug |
Interesting...I will try to debug as well |
There is error when the alt key is used for shortcuts in the library, documented here greena13/react-hotkeys#269 so we need new mappings for translit characters to avoid the long shortcuts |
} | ||
|
||
// export default Shortcuts; | ||
export {ViewerShortcutHanders, ViewerShortcuts, GlobalHandlers, GlobalShortcuts} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great. We should also document the keyboard shortcuts both in the ReadMe.md and somewhere in the application - may be in the footer? @saintsoldierx thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking maybe the help menu (but for another pr) and then a quick help toggle at the top bar
New transliteration keymaps: |
and transliteration shift + key
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. ✔️
Just a suggestion for one more shortcut; can we do shift + v for Larivaar assist?
added shift + l shortcut for larivar assist |
https://drive.google.com/open?id=1ILu1IqxxnFCV8Rs4BAHHC0qTl3CvTdx_6p-EeA--lKY
npm test
& fixed newly introduced lint errors.