-
Notifications
You must be signed in to change notification settings - Fork 171
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
Reminder to remove SD card via Toast notification #424
Conversation
I've tested this on a dev pi2 in raspi-os (thank you for fast screensaver while testing, also showing this on raspi-os which wouldnt be a problem for me if it remained, since it's true). Then I moved onto testing in seedsigner-os on pi0. All works as described above except:
If I never remove the card, I am not reminded. If I remove it and then re-insert the card and forget to remove it, I'm not reminded. I see that MicroSD.warn_to_remove boolean still exists but I don't believe it's being consulted. It was originally added so that the same code that gives a warning to the user can note that it did and avoid nagging. MicroSD thread will set it again if they reinsert the card.... if that helps. As well, I'm able to confuse it in the following way:
This is very nice, unobstrusive, makes a connection for the user between this notification and what they should be looking for (the sd toast overlays). My biased preference would be more reminders if leaving the microsd inserted since it goes away so fast when being actively used ( I enjoyed reading your code changes commit-by-commit as well as the overall diffs. p.s. After leaving this review, and editing multiple times, I saw this from easyuxd and I realy liked it. |
As of 7e964c7:
|
With the recent merge of #423, I was worried there may be plenty of conflicts in this pr since easyuxd was moving icons and colors around, and because everything has been a moving target recently. I've worked to try to resolve some of these so that when you get to doing so, maybe I'll be able to have saved you some time. Conflicts to resolve are:
I think the rest of the merge went without probs, but I know you'll get it right. |
7e964c7
to
c9ac51e
Compare
As of cf2d7b9, ACK tested w/ only one request: to remove attribute 'warn_to_remove' from MicroSD as it's set there but is no longer used/read anywhere else; it's a remnant of pr_410. Why my recent preference for this over pr_410 (or a mix of both for those who want sd-card-removal required)?
|
215e24d
to
3174f09
Compare
* attends to actual microSD state
* Explicit toast control integrated into `Controller` * Coordinate toast vs screensaver Renderer.lock handoffs * Refactor existing toasts to new reusable paradigm
a2f7512
to
fb4a8d8
Compare
Per @newtonick's comments in #437, the notification toast at startup will not be displayed at all if there is user input before the toast's activation delay elapses. |
ACK Tested This PR for MicroSD removal notifications feels right to me now. It provides discovery of the feature (removing the microsd), without creating fear or any barriers leading to confusion. |
As of fb4a8d8, I reiterate my ACK. I note a similar issue mentioned by Nick regarding "awareness of microsd state" as the app starts... to be resolved soon-ish, or maybe with a full-stop version of pr-410? |
Alternative to #410 but builds upon behind-the-scenes updates from that branch. Would close #344 upon merge.
Display a toast notification popup on the Main Menu if the SD card is still inserted.
As has been thoroughly, arduously(!) discussed, my preferred presentation for this notification is to simply let the user know that they can remove the SD card, but omit any mention of security or warnings.
The precursor PR, #410 has evolved into an optional Must Remove hard stop which can work in conjunction with this notification:
BaseToastOverlayManagerThread
implementations.Controller.activate_toast()
to act as a central coordinator to manage theRenderer.lock
between competing toasts, the screensaver, and the currently rendered/rendering Screen.