I also updated SE-Mount to catch flying:
SpecialEvents-Mount-2.0: 4th parameter to SpecialEvents_Mounted and 3rd parameter to SpecialEvents_Dismounted are true if you're on a flying mount.
I'm using SE-Aura-2.0 for Buffalo, listening to the Events
SpecialEvents_UnitBuffGained
SpecialEvents_UnitDebuffGained
SpecialEvents_UnitBuffLost
SpecialEvents_UnitDebuffLost
the problem is, sometimes, they don't get fired on a ReloadUI(). I haven't experienced this on a fresh login yet, but since both procedures are fairly similar, I'm not sure whether or not to trust SE-Aura on login.
Using the iterators on PLAYER_LOGIN is not really an option. Due to the layout system, I can't say for sure which units should be scanned, so I'd have to scan them all and query a decision function on each buff. A full 40 raid would probably kill the client on login. :-(
I'm using SE-Aura-2.0 for Buffalo, listening to the Events
SpecialEvents_UnitBuffGained
SpecialEvents_UnitDebuffGained
SpecialEvents_UnitBuffLost
SpecialEvents_UnitDebuffLost
the problem is, sometimes, they don't get fired on a ReloadUI(). I haven't experienced this on a fresh login yet, but since both procedures are fairly similar, I'm not sure whether or not to trust SE-Aura on login.
Using the iterators on PLAYER_LOGIN is not really an option. Due to the layout system, I can't say for sure which units should be scanned, so I'd have to scan them all and query a decision function on each buff. A full 40 raid would probably kill the client on login. :-(
pastamancer * r23172 SpecialEventsEmbed/SpecialEvents-Aura-2.0/SpecialEvents-Aura-2.0.lua:
SpecialEventsEmbed:
- Auras: if we scan all auras on PLAYER_LOGIN it causes problems with addons whose OnEnable hasn't been called yet. Let's just wait for a real aura event instead.
pastamancer * r23172 SpecialEventsEmbed/SpecialEvents-Aura-2.0/SpecialEvents-Aura-2.0.lua:
SpecialEventsEmbed:
- Auras: if we scan all auras on PLAYER_LOGIN it causes problems with addons whose OnEnable hasn't been called yet. Let's just wait for a real aura event instead.
That did it. Thanks.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumSee http://www.wowace.com/wiki/SpecialEvents-Aura-2.0 for changes. New arguments and return values are in italics.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumbackwards-compatability (and SEE-Mount) should be fixed as of r19274.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumSpecialEvents-Mount-2.0: 4th parameter to SpecialEvents_Mounted and 3rd parameter to SpecialEvents_Dismounted are true if you're on a flying mount.
SpecialEvents_UnitBuffGained
SpecialEvents_UnitDebuffGained
SpecialEvents_UnitBuffLost
SpecialEvents_UnitDebuffLost
the problem is, sometimes, they don't get fired on a ReloadUI(). I haven't experienced this on a fresh login yet, but since both procedures are fairly similar, I'm not sure whether or not to trust SE-Aura on login.
Using the iterators on PLAYER_LOGIN is not really an option. Due to the layout system, I can't say for sure which units should be scanned, so I'd have to scan them all and query a decision function on each buff. A full 40 raid would probably kill the client on login. :-(
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumpastamancer * r23172 SpecialEventsEmbed/SpecialEvents-Aura-2.0/SpecialEvents-Aura-2.0.lua:
SpecialEventsEmbed:
- Auras: if we scan all auras on PLAYER_LOGIN it causes problems with addons whose OnEnable hasn't been called yet. Let's just wait for a real aura event instead.
That did it. Thanks.