Hi Paul, On 05.10.2013 at 20:09 Paul K wrote:
> Hi Andreas, >> I'm trying to understand how wxLua handles its event mechanism. I can see >> that >> for every call to Connect(), wxLua will create a new object of >> wxLuaEventCallback. >> But I don't see where these get deleted. > If you want to delete callbacks explicitly, there is Disconnect() > call. I haven't looked at the wxlua source, but as far as I > understand, callbacks should be removed when Disconnect is called (I > use it in several places in my application). Yes, I know that I can delete them manually via Disconnect() but I'd like to get some more insight on how they're deleted when a window is destroyed and the wxLuaWinDestroyCallback is called which then clears all the wxLuaEventCallbacks pertaining to the window that is being destroyed. But I don't know enough about C++ and wxWidgets to be able to tell where exactly the dtor is invoked. I'd assume that it is the call to Unref() in ClearwxLuaState() but I'm not sure, that's why I'd like to have some feedback on it... -- Best regards, Andreas Falkenhahn mailto:andr...@falkenhahn.com ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk _______________________________________________ wxlua-users mailing list wxlua-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxlua-users
