-
Notifications
You must be signed in to change notification settings - Fork 181
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
Add QR brightness tips screen #389
Conversation
Concept ACK, at the least, and tested I think that this may actually resolve an issue where we've considered changing the default brightness (#377 and #380), because as long as the user knows how to do this, we might not need to default to a strangely dark qrcode background. Also, I really like that there is an Advanced Settings option to disable QR brightness tips, and that it's default=enabled so that new users will see it; they can disable these notices once they learn how important it is. |
Concept ACK |
ACK tested When testing I tried pressing one of the push buttons during the QR brightness tip screen which resulted in skipping the QR instead of skipping the brightness tip screen. |
Thank you, I can reproduce it and will fix it as soon as possible. |
…ing from the QR code page.
ACK Tested |
I think any new UI element (esp if it isn't just a standard 20230630_091655_edit.mp4 |
Thank you for your reminder. I will follow this point in future PRs. |
Super useful feature. Thanks, @overcat! Possible enhancement: I'm thinking it could be helpful to provide the help text in context of the QR code rather than introducing a separate (blank) screen, so I put together a couple quick mocks. Thoughts? @kdmukai, I'm trying to recall if this is what the latest snackbar component looks like. Do you have an example from the current build? |
I like the Brightness Up/Down screen on the left. I think this could be implemented as a GUI component that renders for both static and animated QRs. @easyuxd how do you imagine this help text disappearing/fading out? I think it would be nice for it to flash up for about 1 second and fade out quickly when any QR initially is displayed. Then when the brightness is changed (up or down) it would display again for 1 second and fade out again. |
I love your idea, @newtonick. Here's what it would look like if the snackbar/overlay holds on screen for 1000ms and fades in/out with a standard 300ms transition. |
Hi @easyuxd, if it is an animated QR code, should the QR code change when the snackbar/overlay appears, or should it remain unchanged? |
@easyuxd food for thought (I am in no way convinced this is necessarily a better word choice, though!):
Or perhaps "Dimmer". |
@overcat -- I don't see a reason why the behavior would change. The QR code would continue to animate as usual while the overlay appears momentarily.
@kdmukai Certainly more succinct! Increase/decrease brightness is another option. I don't have a strong preference, myself. Which language are users going to best associate with screen brightness (and when localized to other languages)? |
OK, I raised this question because we now have |
@overcat Thanks for the context. What's the difference between Snackbar and Toast? Do you have a toast example (visual/interaction) you can share? |
When you insert/remove the SD card, you will see this toast. IMG_0088.mov |
@overcat Thanks for the visual aid -- super helpful. We don't need to interrupt the experience unless there's rationale supporting it, like system messaging that users must dismiss. And messaging like this is currently done using Dialogs today so that we can include CTAs: If we think we have 2 distinct messaging use cases that require nuanced interactions (see toast vs snackbar) I'd propose 2 variants of the component: Messaging-Toast
Messaging-Snackbar:
Otherwise (and I think this would be much simpler), we could just align the SD Card messaging with the single messaging component behavior proposed in this PR and have one global messaging component everywhere. This would mean not interrupting users when they add/remove an SD card. |
Hi, I have made some updates and here is the video presentation:
IMG_0091.mov |
Note: suggested refactoring and UI improvements submitted here: overcat#1 |
20230715_093853_edit.mp4 |
* Refactor to use existing components * final tweaks * Update screen.py * Adding comments, TODO
ACK on the latest version of this (incorporates my suggested refactoring and UI tweaks)!! |
ACK ef70a8d It's looking very nice. |
ACK and tested! Awesome work! |
resolve #363
363#issuecomment-1568754458