-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Notification look-and-feel #18
Comments
gavv
added
enhancement
New feature or request
help wanted
Contributions are welcome
discussion
Thoughts, discussions
labels
Dec 3, 2020
Thoughts? |
This comment provides ideas and technical details: #15 (comment) |
Not relevant with new UI. Closing with respect to #49 |
gavv
removed
enhancement
New feature or request
good first issue
Good for newcomers
help wanted
Contributions are welcome
discussion
Thoughts, discussions
labels
Feb 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we use notification with two small text buttons to stop sender and receiver. If the user started sender, notification will have "stop sender" button. The same for receiver. If the user didn't start anything, no notification is present.
Probably the following behavior would be more convenient:
Rationale:
the user usually decides once what they need (sender or receiver or both) and then most times needs to start and stop them according to that decision; so it would be reasonable to have a quick button for that;
one big button to start or stop everything is easier to use;
if the user stopped everything via notification, chances are that they will want to start them back after a while, so it's better to keep notification.
The text was updated successfully, but these errors were encountered: