-
Version: 8.2.5-beta-2 Addons: Descriptions: I use the /fstack command to track the frame levels and record them as follows: 8.0.1 normal: 8.2.5-beta2 normal: 8.2.5-beta2 abnormal: As you can see, when it's normal, the ActionButtonOverlay frame is always on top of the ActionButtonCooldown frame. And if ActionButtonCooldown frame is higher, it would cause the GCD cooldown animation to cover glow effect. It comes into my notice that Masque 8.0.1 changes the frame level of ActionButtonCooldown frame and make it '2', while ActionButtonOverlay frame is '4'. And Masque 8.2.5b does not touch the frames and they are both at level '4'. My guess is that if these two frames are of the same level, the actual generation order are random. Or something else could affect the order, which I haven't figured out. As you mentioned in #67, Masque no longer changes strata of any frames and should not be the cause of this issue, which I think it's undoubtedly right. However, by handling the frame levels as in Masque 8.0.1, it could prevent this kind of issue from happening. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
UPDATE: I am now affirmative that it's the frame level identity between ActionButtonCooldown and ActionButtonOverlay that causes the issue. I type in Strangely, if I use I've tried to read the code of Masque and Blizzard's ActionButton.lua and come to a bottleneck. That is I don't know how to change the frame level of ActionButtonOverlay and get it higher. It seems that ActionButtonOverlay is triggered by native event and couldn't be pre-defined. I've tried to add a line 'Overlay:SetFrameLevel(7)' in Core/Regions/SpellAlert.lua but that just cause all glow overlays on all button frames to be the same, including WAs. I could, however, change the frame level of cooldown frame like Masque 8.0.1. But the base frame level of a Action Button is somehow protected and stays at 3. So that makes ActionButton always at 3, and ActionButtonOverlay always at 4. There is no room left for ActionButtonCooldown . That's all for now. I really want to solve this issue and keep Masque up to date. Any thought would be helpful. Thx! |
Beta Was this translation helpful? Give feedback.
-
After a bit of testing, the cooldown covering the spell alert is the correct behavior. From an objective perspective, if the button is on cooldown you can't use it and the entire button, including its spell alert, should reflect that. Dominos inherits this behavior. The reason that frame level adjustments were removed were due to their increased potential to cause taint. I can't justify reintroducing that risk for the sake of individual preference. If you've a bit of knowledge of Lua, you can code a simple, local add-on that either lowers the cooldown frame of the cooldowns or hooks into the creation/update function for spell alerts and increase their frame level. As an alternative, Bartender4 uses a custom spell alert library and seems to do what you're asking. |
Beta Was this translation helpful? Give feedback.
-
Thx. I'll look into that. |
Beta Was this translation helpful? Give feedback.
After a bit of testing, the cooldown covering the spell alert is the correct behavior. From an objective perspective, if the button is on cooldown you can't use it and the entire button, including its spell alert, should reflect that. Dominos inherits this behavior.
The reason that frame level adjustments were removed were due to their increased potential to cause taint. I can't justify reintroducing that risk for the sake of individual preference.
If you've a bit of knowledge of Lua, you can code a simple, local add-on that either lowers the cooldown frame of the cooldowns or hooks into the creation/update function for spell alerts and increase their frame level. As an alternative, Barte…