On Tue, Dec 21, 2004 at 12:14:29PM -0700, Mike Schroeder wrote: > Mattia Barbon (the maintainer for wxPerl) created a POE::Loop::Wx module > a while back. It worked until the POE 3.003 release, but a few simple > tweaks (looking at POE::Loop::Gtk) was enough to get it working again. > I have attached the module and a minimalpoe.pl wxPerl script. > > I have a few questions for the list (thanks in advance for any help): > > 1) the http://poe.perl.org/?POE_Components_List page lists Michael > Fowler as the author of an unposted version of POE::Loop::Wx. I sent an > email to him back on October but have not received any response. What > is the process for getting this new version on the site?
The site is a wiki. If you look in the page footer, it will ask you to sign up to gain editor privileges. Signup's painfully easy. A link will appear letting you edit the components list. > 2) Would it be possible to get this supported in the main POE distro > (along with Tk and Gtk)? Not likely. In fact, we have vague plans to split the Tk and Gtk event loops out of the main distro. Feel free to appropriate the event loop tests from POE itself. In fact, I encourage their reuse. > 3) It's not quite there yet -- on exit, which calls > Wx::wxTheApp->ExitMainLoop(); > I get the following messages. Being relatively new to this level of > POE internals, any suggestions of how to plug these leaks? > > !!! Leaked session ID: 3 = POE::Session=ARRAY(0x8066448) [... and a lot of other leak messages ...] This looks like ExitMainLoop() is being called while sessions are still active. All the data structures are being cross checked for improper shutdown, and they're coming up with positive hits. Standard operating procedure is to keep the event loop running until after the last user session has stopped. I'll need to install WxPerl to run the test program and find out more. Traditionally I haven't had much luck with WxPerl, though. -- Rocco Caputo - http://poe.perl.org/
