Re: [perl-win32-gui-users] A dynamic popup menu example

Partly because you get a new handle - being more specific, it's because perl does not destroy the menu (the object is stuffed in a global hash, so is never destroyed). If the object were to be destroy in perl, it would call the windows destructor which would release the memory - at least this is

RE: [perl-win32-gui-users] A dynamic popup menu example

Is that because every time you create menu, you get a new handle? I have an app that does this very thing and I have noticed that it grows in memory also. Try doing a Data::Dumper of the object after each recreation to see if the handle is different. Also, what about the subs? I would "expec

[perl-win32-gui-users] New release : Win32::GUI::Scintilla, Win32::GUI::DIBitmap

Hello perl-win32-gui-users, I made new release of my Win32::GUI::* package. See major change : Win32::GUI::DIBitmap V0.14 - Upgrade to FreeImage 3.2 and add new method. Win32::GUI::Scintilla v1.7 - Upgrade to Scintilla 1.59 See more at : http://perso.club-internet.fr/roc

[perl-win32-gui-users] A dynamic popup menu example

Thanks to Peter Eisengrein and Leonard Jacobsen for giving me the pointers to build this example. The code below creates a window with a richtext control. The richtext can be populated with strings separated by commas. When the menu button is clicked, a popup menu is shown, with a sub menu cont