WeakAuras

WeakAuras

206M Downloads

WeakAura frame taint

Evolutious opened this issue · 4 comments

commented

Operating System:

  • Windows
  • Mac
  • Linux

Companion Version:

Check the bottom left of the "About" panel in the app.
Not installed

Companion App Console Log:

Press Ctrl+Shift+I to open the console and copy-paste everything here
Not installed

WeakAuras Version:

/run print(WeakAuras.versionString) in-game.
2.12.0-beta6-7-gff79dcf

WeakAuras Errors:

1. Install https://mods.curse.com/addons/wow/BugSack
2. Install https://mods.curse.com/addons/wow/bug-grabber
3. Try to do whatever it is you're having a problem with again
4. Check your minimap for an icon that looks like a bag.  Is it green, or is it red?
   • GREEN
      • WeakAuras is working correctly.
      • Either you found a behavioral bug, or you are just doing it wrong :)
      • Explain the steps you took, and we will try to figure out what happened.
   • RED 
     • There are error messages. Click on the red bag to see them.
     • Copy & Paste here all of the error messages (there may be more than one, click the 'previous' button on the dialog to see previous ones
No errors reported by BugSack

Describe the bug
A clear and concise description of what the bug is.
My WeakAuras appear to be leaving a taint on my screen where my mouse will not click through them to allow me to interact with the world or anything "under" them. This is not every WeakAura but it is several and it seems to vary on which ones it is with changing occasionally on its own.

To Reproduce
Steps to reproduce the behavior:

  1. Open the WeakAura config window for a few seconds to dispaly your current WeakAuras
  2. run /fstack to enable in game frame analysis
  3. Move mouse over the screen to locate any taints that appear as a green box of the same size and location of existing WeakAuras
  4. Make note of the Frame Stack window and specifically which frame has the arrow pointing to it (it is on the left of the listed frames). This should be pointing to a frame labelled "table: xxxxx" where xxxxx is a random string of characters
  5. Now click and hold your mouse on that area and try to move your screen and you will find that you cannot. Essentially, these areas will not allow the mouse clicks to pass through to the lower frames, one of which would be the world frame.

Expected behavior
A clear and concise description of what you expected to happen.
The taint should not be preventing my mouse from interacting with the frames behind my weakauras when they are not being shown

Screenshots
If applicable, add screenshots to help explain your problem.
https://i.gyazo.com/a2088cf57869456e64e36270c688dd74.jpg Here you can see a taint (green box) and the frame stack in the lower right corner showing the frame is labelled "table: xxxxx". this is with all addons disabled except for WeakAuras.
WeakAuras.zip

Include a .zip file containing:
%programfiles%\World of Warcraft\_retail_\WTF\Account\<AccountName>\SavedVariables\WeakAuras.lua
AND
%appdata%\weakauras-companion\config.json

commented

Hey I am getting something similar. Mostly noticed it because of having tooltip enabled for them https://i.imgur.com/UBjpxeO.gifv . Here's an aura for it https://wago.io/88zGFpY2z It's TSU aura, but I am not really doing anything dodgy there that should break it. Here's frame stack of it https://i.imgur.com/F53bCas.png
Also here's aura with default triggers that does similar thing except for showing tooltip but still captures mouse clicks. https://wago.io/bnn6fVYtx https://i.imgur.com/ZgAggzu.gifv fstack - https://i.imgur.com/U6vORMu.png
Seems to be related with cloning auras for me (TSU, Auto-Clone) as I couldn't reproduce with "standard" aura

Im on ff79dcf
No idea when exactly this started

commented

Rolling back to release 2.12.0-beta6 fixes my issues so it appears to be something introduced in the latest alpha releases.

commented

Seems to be related with cloning auras for me (TSU, Auto-Clone) as I couldn't reproduce with "standard" aura

You know, now that i look it is also for me with any WeakAuras that are doing clones. Maybe that is the trigger!

commented

Rolling the builds forward and testing, this was introduced in release: 2.12.0-beta6-5-g658d1f8