Skip to content
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

Notifications don't stack, stopping watch use after display power on #117

Open
dodoradio opened this issue Dec 20, 2022 · 0 comments
Open

Comments

@dodoradio
Copy link
Contributor

When the display is turned on, a 'recap' of new notifications is presented. The notifications are presented one at a time and each one disappears with a tap or after a few seconds. This works very well, but if the number of notifications is above a certain number, it can take a significant amount of time to clear all the notifications, which can make the watch unusable until all notifications are cleared. This is especially a problem with the 'connected'/'disconnected' notifications emitted by asteroid-btsyncd, though that is probably a separate issue.

It has been discussed that notifications should present as currently, but after a certain number (for example, five) the last should just show how many more notifications there are, so the user can then manually check them in the launcher.

@dodoradio dodoradio changed the title Notifications don't stack, breaking usability Notifications don't stack, stopping watch use after display power on Dec 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant