-
-
Notifications
You must be signed in to change notification settings - Fork 315
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
Conditional Custom Options #4496
Comments
Not a bad idea, but I think the ask would be better answered via exposing hidden/enable from the underlying ace config API. |
I like this idea. Here is how I think it could be implemented. To the user, they should simply be greyed out or not depending on other Custom Options. For the author, each Custom Option should have a Requirements section where to select a checkbox or insert the name to indicate which Custom Options are needed for it to be clickable, not greyed out. |
Is your feature request related to a problem? Please describe.
The current implementation of custom options in WeakAuras for World of Warcraft lacks the ability to conditionally show or hide certain options based on the value of other options. This limits the customization potential and can result in a cluttered interface.
Describe the solution you'd like
I would like to request the addition of conditional custom options in WeakAuras. This feature would allow for the dynamic display of options based on the value selected for a specific option. For example, if the user chooses "Type" as "Second," relevant custom options related to the second type would be shown, while they would be hidden if the user selects "First" type. This enhancement would significantly improve the user experience by providing a cleaner and more streamlined interface.
Describe alternatives you've considered
Currently, the only workaround is to include tooltips or instructions to guide users on which options to leave empty or not use. However, this approach can still lead to confusion and isn't as user-friendly as having conditional custom options.
Additional context
I would imagine it looking something like this and inside the Author mode it would be like a normal Option Group but with a Visibility Option that could be like the normal Conditions for Example typeSelection == 2
The text was updated successfully, but these errors were encountered: