-
Notifications
You must be signed in to change notification settings - Fork 182
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
Resolves issue 555 - Improve UX navigating across DEL button (expanding it) #603
base: dev
Are you sure you want to change the base?
Conversation
Growning "del" button size property (from 2 to 3) solves navigation issue ("6th dice" -> "del"). solves issue SeedSigner#555
Additional differents sizes "del" buttons
new custom_additional_keys prop on KeyboardScreen class for can to change additional button (KEY_BACKSPACE) on its childs classes
Changing KEY_BACKSPACE size on BIP39, SeedBIP85, SeedCustomDerivation, symbols_1, symbols_2 screens
Changing KEY_BACKSPACE size on ToolsDiceEntropy and ToolsCoinFlip screens
Branch renamed for better understanding. |
Missed import sentence for commands on last commit
Fixed missed import sentence on tools_screens.py |
#555 link |
First of all, thank you @fedebuyito ! As of 3c967a0
Pending code review regarding the KEY_BACKSPACE object. |
concept ACK |
Code adapted (and tested on emulator) in order to resolve conflicts from last massive merge (PR #620 ) |
Code adapted (pytested and tested on emulator) in order to resolve conflicts from merge PR #664 : |
Description
This Fixes #555 wich aims to improve user experience when navigating the screens where KEY_BACKSPACE/DEL button is showed. Expand DEL to fill any remaining gap would fix what reported on issue.
Include screenshots of any new or modified screens (or at least explain why they were omitted): Here screenshots, before and after, #555 (comment)
This pull request is categorized as a:
Checklist
pytest
and made sure all unit tests pass before sumbitting the PRIf you modified or added functionality/workflow, did you add new unit tests?
I have tested this PR on the following platforms/os:
Note: Keep your changes limited in scope; if you uncover other issues or improvements along the way, ideally submit those as a separate PR. The more complicated the PR the harder to review, test, and merge.