Refresh uvars and Combat Text events on FCT SetValue #4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
basicOptions.lua
Outdated
| info.func = function(self) | ||
| addon:SetCVar("floatingCombatTextFloatMode", self.value) | ||
| UIDropDownMenu_SetSelectedValue(dropdown, self.value) | ||
| if not InCombatLockdown() then |
Owner
There was a problem hiding this comment.
Is InCombatLockdown() needed here? We already close the options when combat starts and they can't be opened in combat anyway.
Contributor
Author
There was a problem hiding this comment.
Ow, I still managed to keep the options window open somehow, but removed that unneeded conditional now
Owner
|
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates the FCT events when changing the "Scrolling Combat Text for Self" options, otherwise a /reload or relog would be required for the changes to show up