-
Notifications
You must be signed in to change notification settings - Fork 36
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 button to dismiss "Set as default launcher" message #2325
Comments
Thanks for your suggestion! Sorry, I don't think adding a "Dismiss" button to turn off the prompt completely will be a good idea; There is a possibility that some users might accidentally dismiss the prompt, and they may have difficulty setting Niagara as their default launcher, especially if they are unfamiliar with the process of changing launchers. Additionally, the user base that use Niagara in combination other launcher is relatively small. If one prefers to use it this way for any reason, we have this secret command in place that allow the users disable the prompt. However, I would love to know, what benefits do you see in having a button in place, as opposed to a secret command? |
Despite searching the help pages, I couldn't find the secret command. Having a button would make it easy for people who can't find it (or don't look for it) to hide the message. The button doesn't necessarily have to be built into the message. Adding it to the settings menu could also work. |
Thank you for your explanation! From my perspective, if someone isn't looking for this option, they shouldn't be bothered by not having the "Dismiss" button. It's also worth mentioning that we only consider adding an option if there is significant demand and it aligns with our design guidelines: I apologize, but currently, we do not have plans to include the button or an option to dismiss the prompt in Niagara settings. However, if we change our stance in the future, we will update the issue accordingly. Thanks, |
Is your feature request related to a problem?
#2323
This should not require a secret command.
Describe the solution you'd like
There should just be a button to hide it.
Feature Request Procedure
The text was updated successfully, but these errors were encountered: