Window Hook

Skye · Post by **Skye** » Tue May 04, 2004 11:56 pm

Looking for a piece of information on the startup sequence of events/hooks.

BACKGROUND
I spiraled into debugging a previously working script today - going out of my mind - a very simple macro was breaking: ${Window[blahblah]} was always returning NULL.

OBSERVATION
After some black-box debugging (I was just looking for the "Adding WndNotification target '%s'" message being sent to my log file), it seems to me that the MQ2Windows.cpp:SetScreenHook.SetScreen_Detour is only called if MQ2 is started before EQ. Voila, the macro would respond again once I started them in the right sequence.

Is this true?

dont_know_at_all · Post by **dont_know_at_all** » Wed May 05, 2004 12:07 am

No. MQ2 hooks the functions but they are not called from EQ if UI is already initialized. /loadskin or restart will fix your problems.

Skye · Post by **Skye** » Wed May 05, 2004 12:57 am

Thank you for the quick response, DKAA. I could tell that the hooks were being called only at initialization ... since I have never used different skins, using /loadskin never occurred to me! I do appreciate the pointer.

Lax · Post by **Lax** » Wed May 05, 2004 1:22 am

yes what is happening is, MQ2 hooks the initialization of the windows. If it doesnt catch the initializations, it doesnt know what windows are open. Currently we dont have a way around that, but one might pop up soon.