Simulating events

[Jesus72]

Hi,

I'm wondering if it's possible to send events that will be picked up by whatever is subscribed to that event?

I'm trying to debug something but it's quite difficult without actually doing the event.
I know I can send a false event to a specific OnEvent function but can't seem to recreate the issue that way.

The alternative question is, any reason why a prehook would fail to run when in LFG dungeon but work perfectly in a LFR raid?
Thanks

[SDPhantom]

You can use GetFramesRegisteredForEvent() to get a list of frames that has the event registered. After that, you can try to grab each one's OnEvent handler and run it. Don't forget to include a reference to the frame itself and the event firing among the list of arguments when calling a frame's handler.

function FireEvent(event,...)
    local framelist={GetFramesRegisteredForEvent(event)};
    for i,j in ipairs(framelist) do
        local func=j:GetScript("OnEvent");
        if func then func(j,event,...); end
    end
end

In essence, LFD and LFR have two different sets of frames even though Blizzard has been trying to integrate them into the LFG template. It's one mess I really don't want to dive into.

[Jesus72]

Ah that's great, thanks.

This seems to recreate the issue I'm facing.

Seems that if I call the frame's OnEvent directly as BlizzardFrame_OnEvent(BlizzardFrame, EVENT, ...) my prehook kicks in and works.

If I try and call it as you did using GetScript("OnEvent") my prehook gets ignored.

[SDPhantom]

What happens a lot is Blizzard defines the function in Lua, then links it in XML. This means the Lua function isn't really called anymore from the global namespace where your hook resides. You need to hook the frame's handler directly.

To understand this better, when you hook a function, you're essentially creating a new function that calls the old one. Right now, you're just sticking it in the global namespace where the old one was. However, when the function was registered as a frame's handler, it stored the pointer to the old function and continues calling it directly. A cheap way to have your hook apply to the frame's handler is to re-register it.

BlizzardFrame:SetScript("OnEvent",BlizzardFrame_OnEvent);

[Jesus72]

Originally Posted by SDPhantom What happens a lot is Blizzard defines the function in Lua, then links it in XML. This means the Lua function isn't really called anymore from the global namespace where your hook resides. You need to hook the frame's handler directly. To understand this better, when you hook a function, you're essentially creating a new function that calls the old one. Right now, you're just sticking it in the global namespace where the old one was. However, when the function was registered as a frame's handler, it stored the pointer to the old function and continues calling it directly. A cheap way to have your hook apply to the frame's handler is to re-register it. BlizzardFrame:SetScript("OnEvent",BlizzardFrame_OnEvent);

Thanks, that helps a lot.

Managed to get it working like this