I'm running standalone... and it's not only AceEvent-2.0 it's TabletLib-2.0 for me too. But I'm running also Arkinventory and errors ocurs for me only at the mailbox/disenchanting/prospecting...
Updated several addons today and booooom, the memory allocation errors from AceEvents.
Mostly during mail, bag, scan activities.
Then I saw the realy, realy huge memory consumptions and increasing rates from BtmScanner/Auctioneer.
Downgrades Auctioneer now back to 5.0.PRE.2887 (from where I updated today) - much less increasing rates and no errors till now.
You could do it like KTM does:
At the time the master target is set - if you can't find a target with the name, take the target of the player who send you the master target. Thats probably the master target send in your locale...
Bartender3 is not usable with my rogue at the moment.
The keybindings for the mainbar "locks" for the stance i am when entering combat.
So after attack somthing out of stealth, the bar switches to the right actions - but the keybindings are still as though i were in stealth.
Bartender3 is not usable with my rogue at the moment.
The keybindings for the mainbar "locks" for the stance i am when entering combat.
So after attack somthing out of stealth, the bar switches to the right actions - but the keybindings are still as though i were in stealth.
venjens - I think you should again look at the ParserLib and try to understand what it does before posting enhancement suggestions nobody understands...
I think you underestimate ParserLib and the parse engine behind it and what it does. The engine is a very abstract and generic.
It does not listen to specific events and parse each event for it own. It has an engine with which is it easy to include more events in a very nice an quick way.
You also should concern, that incomming events are mapped on several outgoing events and that it's not a one to one relation.
The suggestions from you would only decrease the object oriented and generic approach - and with it the maintanability.
Look at SW_Stats - it was at the time a unique way to parse the combat messages without localization based string searches. So the parsing would do it in every language. It helped me a lot to understand ParserLib.
0
0
0
Mostly during mail, bag, scan activities.
Then I saw the realy, realy huge memory consumptions and increasing rates from BtmScanner/Auctioneer.
Downgrades Auctioneer now back to 5.0.PRE.2887 (from where I updated today) - much less increasing rates and no errors till now.
0
At the time the master target is set - if you can't find a target with the name, take the target of the player who send you the master target. Thats probably the master target send in your locale...
0
But according to http://www.wowguru.com/db/spells/spiteful-fury-id36886/
it should be "Boshafter Furor".
0
Sorry - the new version r19826 fixed it for me
0
The keybindings for the mainbar "locks" for the stance i am when entering combat.
So after attack somthing out of stealth, the bar switches to the right actions - but the keybindings are still as though i were in stealth.
0
Much faster than a reloadui...
But the answer keeps the same: there is still no standard x)
0
I think you underestimate ParserLib and the parse engine behind it and what it does. The engine is a very abstract and generic.
It does not listen to specific events and parse each event for it own. It has an engine with which is it easy to include more events in a very nice an quick way.
You also should concern, that incomming events are mapped on several outgoing events and that it's not a one to one relation.
The suggestions from you would only decrease the object oriented and generic approach - and with it the maintanability.
Look at SW_Stats - it was at the time a unique way to parse the combat messages without localization based string searches. So the parsing would do it in every language. It helped me a lot to understand ParserLib.
Btw: Someone want to Ace SW_Stats? :P
Sorry, couldn't hold off the comment ;)