-
-
Notifications
You must be signed in to change notification settings - Fork 446
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 "don't show again" checkbox to setup assistant #433
Comments
Hello @Yukai-Qian, this is happening because you are using EverythingToolbar in a quite unconventional way by launching it via the desktop shortcut rather than the taskbar icon. I like your suggestion of adding a checkbox "don't show again" to the setup assistant! |
@srwi thank you for accepting my idea! I look forward to the update. |
As a workaround, I found that putting EverythingToolbar.lnk into |
I added a popup dialog that asks if the user is sure they want to prematurely end the setup process. This will prevent the assistant from popping up again. It will still be accessible via the system tray icon. This will be available in the next release. |
Preflight Checklist
Problem Description
Hi, first of all this is a great app and I'd like to continue using it. However this has been a minor annoyance. At every startup, if I don't have a search icon pinned to the taskbar, the app will launch the setup assistant and ask me to do so. I eventually had to pin the icon just for the app to stop asking.
I have configured a shortcut for EverythingToolbar and even if I pin an icon to the taskbar, I would not click it anyway. If I will need to move my hands to the keyboard to type the search query, then I might as well launch EverythingToolbar with a shortcut instead of using a mouse.
Proposed Solution
It would be nice if the setup assistant does not open just based on whether there is a pinned icon.
Alternatives Considered
I've considered just pinning the icon and calling it a day. But I'd still like to suggest not to ask the user again if they decide not to.
Additional Information
No response
The text was updated successfully, but these errors were encountered: