UseQuestLogSpecialItem vs. the world
Dear Blizzard,
Your new objective tracker is the most delicate of flowers in a winter storm. Even looking sideways at seemingly unrelated things, like the world map, poisons it, rendering its quest item buttons unusable. It's even worse than the infamous and still-overly-sensitive-after-all-these-years UIDropDownMenu system. You could solve the quest button problem very easily by making the UseQuestLogSpecialItem only require a hardware event, rather than it being a completely protected function. I understand you don't want addons automatically using quest items without the player making decisions, but I really don't see any serious potential for abuse if it requires a click/keypress. It's a quest that probably takes 5 minutes and zero thought beyond looking for the dot on the map -- side note: WTB epic quest chains back from vanilla! -- not raid progression or tournament PvP. |
*sign with 10 letters*
|
I've never used that API, but coincidentally I was thinking about it yesterday. Is it possible to securely hook UseQuestLogSpecialItem()? I'd imagine that would solve most of the problems.
|
Quote:
Code:
hooksecurefunc("CastSpellByName", function(spell, target) |
Signed here too ... I was quite surprised that literally reparenting the main frame broke the buttons security.
What makes it worse is that some of the items aren't physically in the bags to use manually that way, so I sure hope those ones work by clicking on the mobs in question. |
...Signed...
I do use the addon http://www.curse.com/addons/wow/questitembuttonfix, but Blizzard has broken all quest addons. |
Yes please! This keeps breaking for me and I've absolutely no idea why.
|
Hmm Interesting ..
Managed to get it not error out in my addon with the following minimal code: Lua Code:
frame being a ScrollFrame parented to UIParent or with nUI Infopanel as necessary. However, this offsets the tracker lines too far to the left and and makes the POI Icons and check marks not appear properly or at all. The line that fixes that is : DEFAULT_OBJECTIVE_TRACKER_MODULE.blockOffsetX = 30 But the moment you use that or any of the specific modules versions it kicks out the error. Also, the use of these two lines after that code (although not sure if I need it now I'm not re-parenting as such) also produces the error. ObjectiveTracker_Update() QuestObjectiveTracker_UpdatePOIs() The moment I remove those 3 lines from the equation it allows you to click the button. Edit: I wonder if creating your own module stops the error. Might have to be something to look into at some point. |
After reading Resike's post elsewhere regarding this problem and I have rigged up the following mini addon.
Lua Code:
Feel free to try it out .. the questitems don't taint as long as I don't use that blockoffset value, if I don't use the blockoffset value it misaligns as it uses that every update to set the alignment of each block. |
All times are GMT -6. The time now is 05:02 AM. |
vBulletin © 2024, Jelsoft Enterprises Ltd
© 2004 - 2022 MMOUI