Skip to content
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

Anchoring to frame that is not always loaded/triggered fails to maintain position #143

Closed
Konghol opened this issue Jan 27, 2017 · 3 comments

Comments

@Konghol
Copy link

Konghol commented Jan 27, 2017

What steps will reproduce the problem?

  • create a WA Icon (Calling it WA_1) that has a display trigger and load conditions
  • Create another WA Icon (Calling it WA_2) that is anchored to WA_1
  • Issue: Zoning when WA_1's display triggers are not met and load conditions are not met can sometimes result in WA_2's position to be completely out of place. Seems to happen inconsistently.
  • Note: To resolve the issue, I simply had to go to WA_2, and press enter on the selected frame text entry (i.e. did not change selected frame text, just pressed enter on it to "refresh" the selected frame)

What is the expected output? What do you see instead?

  • WA_2's position to always be anchored to where WA_1's position would be.

Did you try having WeakAuras as the only enabled addon and everything else (especially something like ElvUI) disabled?

  • No. ElvUI is enabled

What version of WeakAuras are you using?

  • 2.2.2.6

Was it working in a previous version? If yes, which was the last good one?

  • No, previous version I use did not support anchoring to frames

Do you have an error log of what happened? If you don't see any errors, make sure that error reporting is enabled (/run scriptErrors 1) or install BugSack.

  • Bug does not generate an error

Please provide any additional information below.

  • I love the anchoring of frames! Can't wait till all the bugs are worked out. Keep up the good work dev(s)!
  • I'm pretty new to WAs. Sorry if some of the terminology I used seems off.
@InfusOnWoW
Copy link
Contributor

If WA_1 display triggers are not met, WA_2 should not be visible.

Do the load conditions differ between the auras?

@Konghol
Copy link
Author

Konghol commented Jan 27, 2017

The load conditions are the same. Basically, in-combat/spec/talent requirements for the load condition.

Is there a loading order to WAs? Perhaps the anchored WAs tried to load before the WA they were anchored to and lost position as a result.

I'll try to provide a more specific use case when I get home tonight.

@InfusOnWoW
Copy link
Contributor

I did a change that should ensure that the aura always gets attached to the right parent just before being shown. Thus I think this should no longer happen in the next alpha.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants