-
-
Notifications
You must be signed in to change notification settings - Fork 672
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
T3T1 UI - passphrase flow improvement #4094
Conversation
|
cc @lapohoda |
@Hannsek UI changes briefly: |
@obrusvit pls doublecheck the size of confirmation button – should be circular according to Figma 👇 .. Otherwise it is ok👍 |
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.
utACK.
general note: it's not great that you're adding Text(ShortString)
in there, and especially not great that you're adding it to the passphrase Confirmed() variant. What we originally intended with ComponentMsgObj (on the model_tt side) is that you return a "user is done" message, then the ComponentMsgObj impl asks the layout to give out a &str
, and we convert that to micropython.
Here, we'd want .map()
to pass you both the original layout and the returned message -- so that you can do this part in the map()
closure.
on the other hand, i'd prefer getting rid of Map
component the way we use it now. and currently doing it like this fits well with overall way of doing things in mercury. We can refactor the things when refactoring time comes, i guess.
This commit allows flows to work with ShortString which can be converted to micropython as str. [no changelog]
[no changelog]
7e86a32
to
9bca204
Compare
This commit adds a Component which prompts a user with a pair of two buttons - left and right. The Component is parametrized by the buttons contents and styles. [no changelog]
[no changelog]
PromptScreen now uses dedicated PromptMsg with Confirmed and Cancelled values instead of empty Option<>. This change affects only mercury code. This is more explicit and enables "yes" or "no" prompts screens. Otherwise, the "no" option was handled by the 'x' button handled by Frame. [no changelog]
This commit replaces request_passphrase with flow_request_passphrase. The added benefit is that the user is prompted for confirmation if they want to proceed with an empty passphrase.
[no changelog]
Usage of different copy in mercury (especially titles and subtitles) requires moving the layout code deeper into the model specifics. [no changelog]
9bca204
to
a1fdfbe
Compare
[no changelog]
|
Merging amidst |
This PR adds reassuring screen when entering empty passphrase.
In order to do that, this includes some necessary changes:
FlowMsg::Text
variant which enables passingShortString
to uPy asstr
. Btw.ShortString
is conveniently limited to50
chars which needs to be revisited if we implement Remove 50 character limit from passphrase #4084 (comment)PromptMsg
instead of passing emptyOption
around. This has the benefit that theBinarySelection
from ebc297f can be used asPromptScreen::new_yes_or_no()