First child of a group has a different frame level than the other auras in that same group #4741
Comments
github-actions
bot
added
the
⏱ Awaiting Response
|
With your setup the icons are in the frame strata medium. The PlayerFrame is also in the frame strata medium. The exact ordering of frames in the same frame strata depends on the frame levels. WA automatically assigns frame levels to auras in a group, to minimize interference between auras in the same group. But for ordering between the game's frames and the group, you have to use a different frame strata. |
|
Before the changes in commit f00565f, all Auras in a group would appear above the parent anchor. After the changes, only the first entry in a group appears below the parent, with all others being displayed as they always have. This stays consistent even if you re-order the auras in a group. You can leave the auras themselves untouched, but if you move an aura into the first slot of a group, its frame level changes, as does the frame level of the aura that used to be first. This behaviour seems unwanted to me, especially since it didn't used to do this in previous versions. I would expect that changing the order in the group should have no impact in relation to other frames, but only to other auras in the same group. In a more general sense, it seems off that a function only applies to the first aura in a group and not all of them. Looking at the code in commit f00565f, it seems likely that the original frame level that is assigned to the auras in the group is consistent, but that the frame level of only the first aura in a group is at some point overwritten, causing this behaviour to occur. |
|
Yes the behaviour has changed slightly. No what you describe is not a correct. The frame strata is applied to all children. Again, the PlayerFrame is on the same frame strata as your auras, which then leads to the order depending on the frame level. |
|
Your first reply made me aware that my initial interpretation was incorrect and that this does not relate to frame strata, that all auras are still on the same one. However, in my last reply I did not mention strata at all, I merely talked about frame level, and about how I think the frame level of only the first entry in a group is overwritten, and thus creates the situation that that aura has a different order within the strata compared to the other auras in the group. So keeping that in mind, how is my description not correct? Or if it is correct, is this behaviour not unwanted? |
|
The frame level is not overwritten. Again, as I already explained: But for ordering between the game's frames and the group, you have to use a different frame strata. |
|
In the screenshot I provided I have 2 images of the same group of auras with exactly the same settings within the individual auras. The only difference is that the left image has the top left icon in the first entry of that group, whereas the right image has the top right aura in the first entry. So only the first entry appears behind the player frame, whereas the others do not. Do you know why this happens and could you explain that to me? And more importantly, if I revert the changes in commit f00565f, and only those changes, this no longer happens. With those couple of lines reverted, changing the order of the auras in the group changes nothing, and regardless of order all four auras appear in front of the player frame. I understand that frame strata does not play a role here at all, in all cases the player frame and auras all remain on the same strata. And if you say that frame level is not changed or overwritten, what else is causing this behaviour? |
|
It seems that my issue is closely related to issue #4718. The commit that I mentioned multiple times as the cause of my issue, f00565f, was part of an attempt to fix this other issue. Although details differ, dynamic vs normal groups & retail vs classic, and our issues have come and went with different WA versions, the core seems very similar: The first entry of a group does not seem to get the same frame level as other auras in the group, causing unwanted and unexpected behaviour. |
Ricodyn
changed the title
No, it's unrelated. #4718 is an issue because we assign the wrong frame level to the backdrop of the group, and thus the automatic assignment of frame levels lead to the auras being behind the backdrop. Your "issue" is about the ordering between a group and frame that is provided by the game. And for that I can only repeat myself: There are no gurantees what the relative frame level of auras vs unrelated frames is. |
Is there an existing issue for this?
Description
The first WeakAura in a group doesn't always have the same frame level as the other auras in the group. Reverting the changes in commit f00565f fixes this.
WeakAuras Version
WeakAuras 5.8.7
World of Warcraft Flavor
Retail (Default)
World of Warcraft Region
EU
Tested with only WeakAuras
Lua Error
No response
Reproduction Steps
Create a group and create an Aura in that group.
Set 'Anchored To' to 'Select Frame' and check 'Set Parent to Anchor'.
Select a Frame, for example the PlayerFrame or a bar button.
Duplicate the Aura.
The first Aura (top child in the group) seems to have a different frame level from the duplicate.
Last Good Version
Weakauras 5.8.5
Screenshots
The only difference between the two images is which aura is the first in the group. That first child appears behind the character frame and seems to have a different frame level from the other auras, as the other 3 appear correctly in front.
Export String
The text was updated successfully, but these errors were encountered: