#Anchoring WA to LFG

1 messages · Page 1 of 1 (latest)

tribal karma
#

I have a WA that's position is anchored on the LFG panel. However, when I log into a character initially the WA is not anchored to the LFG panel until an event has fired from one of my triggers.

The trigger events are PLAYER_ENTERING_WORLD,WA_DELAYED_PLAYER_ENTERING_WORLD,VARIABLES_LOADED,LOADING_SCREEN_DISABLED,ENCOUNTER_END,PLAYER_LEAVE_COMBAT,PLAYER_REGEN_ENABLED,CURRENCY_DISPLAY_UPDATE,QUEST_TURNED_IN,PLAYER_LEVEL_UP,GLOBAL_MOUSE_DOWN,GLOBAL_MOUSE_UP
If I change this to Every Frame it works but that seems like overkill for my situation.

I assume PLAYER_ENTERING_WORLD would be sufficient but that doesn't seem to be the case.

opal warren
#

PLAYER_ENTERING_WORLD triggers before weakaurs is loaded.
Use WA_DELAYED_PLAYER_ENTERING_WORLD

tribal karma
#

That event is listed second in my list.

peak agate
#

Why do you have a thousand events listed there? How do you anchor your frame to the lfg window?

#

That looks like you just started to list all kind of random events

tribal karma
#

How do you anchor your frame to the lfg window?

#

Why do you have a thousand events listed there?
I have 12. I did base this on another Wago, but the events are things that would trigger badge collections to recalculate your current amount.

peak agate
#

There is a event for getting currency, all others are wrong

tribal karma
#

In what context? How does that effect my issue I'm seeing? I have other actions that enable/disable views on my WA based on mouse clicks.

peak agate
#

Without seeing the full weakaira, as it seems very complex, I can't tell you what goes wrong. I also have to go to work now and can't look at it. But you can post the aura and someone else can look at it

#

But having 3 events for logging in shows something is foshy

#

It's 4 events

tribal karma
peak agate
#

To wago please, that just makes it harder to look at

tribal karma
#

Click, ctrl-a the file then ctrl-v into WA no?

peak agate
#

Many of those that help out don't have wow open right now or aren't even on a computer

#

It's possible to read the Lua table in the case of a non custom trigger, it's impossible to read the encoded gibberish.

#

Wago allows it to read the actual code too without being on a computer.

tribal karma
opal warren
#

!clickable

tacit cosmosBOT
opal warren
#

the way you structured this you might as well just make an addon

peak agate
#

The first they will ask in the ticket is to remove all mentions and changes to the region. That can and will make problems.

tribal karma
#

Regardless of my WA implementation. None of that addresses my original issue. I've created a smaller WA to reproduce what I'm seeing https://wago.io/8sYmh8I6S

Wago.io is a database of sharable World of Warcraft addon elements

tribal karma
#

The anchor works after I load up the WA menu and close it.

I can fix the issue to anchor the WA properly if I add a dummy default trigger (the configuration from just clicking add trigger).

#

But I'm still wondering why WA_DELAYED_PLAYER_ENTERING_WORLD wouldn't trigger it to anchor correctly on logging in.

tribal karma
#

Any feedback on the issue with anchoring to LFG with my simplified WA?

peak agate
#

!ticket if you have an simple example

tacit cosmosBOT