-
Notifications
You must be signed in to change notification settings - Fork 121
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
Feature Request: Warning if Duplicates Detected #484
Comments
Sorry for the late response. It would sure be possible to add such a dialog! Currently there are two settings for ignoring duplicates: The app can ignore duplicates that happen directly after each other or avoid any duplicate in the whole history. I think such a dialog would probably only be useful for the latter option. Still, I am wondering if a dialog is the best choice here since it would require some user interaction. Which could get annoying, I'm afraid. So maybe a (toast) message would be better if you are just interested in when a duplicate was detected? |
Sure a toast notification could work. About the annoyance should it otherwise be a dialog box, that can be solved by having additional options in the settings under "Ignore Duplicates" such as:
|
Well, with the existing three possibilties:
This would result in something like this:
Feels a bit like feature creep to me 😉 Of course, the silent/toast/dialog option could be another setting. |
Sure, that'd be a lot to take in and ruin the simplistic nature of the app:
Under the Feature, I'd keep these options
|
I have been enjoying using Binary Eye for about 2 weeks now.
I understand of the Ignore Duplicates and History Feature. Currently when those two features are enabled and a duplicate is detected, it's ignored silently.
The request I'm making is a build-up on these two, if there could be a toggle to allow the app to show a warning pop-up with or show some visible feedback when a duplicate is detected.
I have tried to make a mock-up of the pop-up below:
Don't mind the sloppy design ;)
The text was updated successfully, but these errors were encountered: