-
-
Notifications
You must be signed in to change notification settings - Fork 680
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
Delizia tap-to-swipe hotfix #4571
base: main
Are you sure you want to change the base?
Conversation
e0c31d3
to
e581a3d
Compare
|
39f7ee6
to
e12346a
Compare
Monero failure is spurious. Perhaps #3463 will help with those. |
TODO:
translations: DE: Zum Fortfahren tippen |
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.
A few comments for now, I'd like to review and test more later on.
I think we can proceed with the points from @Hannsek
|
Can we do even more? |
what do we think about replacing the same string id? |
Having "Tap to confirm" under I'm in favor of introducing the new one. |
we translate "Tap to confirm" as "Appuyez pour confirmer", we should probably use the same word here?
"Tocca e continua", same as "hold to continue" is "Premi e continua" ?
so we're getting rid of "tap to start"? also we need translations for the new text:
|
i mean, we can fully rename the key π€·ββοΈ |
PaginateFull uses Pager instead of reporting just the total number of pages. Delizia will rely on this trait; going forward, we'll want PaginateFull to replace Paginate, but this refactor would be too big if we also needed to include Caesar and Bolt in it
We introduce a new variant FlowMsg::Next, used only internally (for now). Sending FlowMsg::Next indicates we want to proceed to the next screen of the flow. If there is internal pagination, Next will play a simulated swipe to the child component.
this generally simplifies the mappings of Frame messages, but also relies on the button actions being properly set up.
when animations are disabled, hold-to-confirm has zero timeout
e12346a
to
88daace
Compare
these two are the same thing. i tried to extend over the whole screen except header, please test
done
done |
I'll do final pass including the tutorial later on. |
Does swipe down to go back work? |
They are not. The first one is about the confirmation screen where the middle confirmation button is. |
This implements tap-to-swipe functionality on Delizia, to avoid problematic swipes.
points of interest:
PaginateFull
trait that is usingPager
instead of just returning a total. this is used throughout Delizia, for now the originalPaginate
is kept for backwards compatibility.the big changes in above are refactors of
Paragraphs
andFormattedText
pagination, where we don't have to go from the beginning every time, because we now remember on which page we are (until then we only knew on which offset in source data we are)8dc1e12 is the big hotfix -- introduce a virtual button in
Footer
and respond to clicks to that button by (a) replaying an artificial swipe to an internally swipable component, or (b) returningFlowMsg::Next
up the stack, forSwipeFlow
to pick up, which should respond byNext
this way all the flows written to work with swipe-up will magically also work with footer-click
the rest are some patches for some problems.
another important refactor in cf490d0 is that
Frame
now has its ownmap()
function that maps only the content message to something. Messages from button(s), either header or footer, are always mapped to themselves.