Closed arnath closed 15 years ago
Because I save a local reference before you're hooking.
Naturally I question why you hook, hooking should be a last resort.
Right now I do some processing both before and after calling Blizz's WatchFrame_Update() function. I'd avoid this problem by using a secure hook instead, right?
Secure hooks fire only after the function in question.
Well to elaborate, my options are either to do what I do now (raw hook) or to basically run WatchFrame_Update() twice every time it is called because I resize the WatchFrame and Blizz's function won't update to the new size if I do so after the update happens.
I've not delved deeply into it, but I did notice two things about the new watch frame... it uses a frame's width as the max width, and it seems to ignore width entirely if the frame is on the left half of the screen. Personally, I was thinking about tricking into always thinking it was on the left, and the tinkering with the position by hand probably. or maybe just forcing the frame to be wider...
Thanks, I figured out a way to avoid hooking the function that involved just telling it the frame was on the left side of the screen before I resized.
I have a mod called Inquest that among other things, does a lot of stuff with the quest tracker for which I hook WatchFrame_Update(). I know that my hook works just fine because I see tons of WatchFrame_Updates get processed correctly. However, for whatever reason, the call to WatchFrame_Update() on line 72 of Broker.lua in TourGuide seems to not call my hook and calls the original function somehow. Do you know why this is/how I might be able to fix it?