Is this considered...ummm... "normal" behavior?? What is it about the architecture of the Win32GUI modules that makes it work this way? It is really the most peculiar thing I have ever seen, and breaks every model for OO programming that I know of... (i.e. that the contents of an object must be maintained as references outside of the object for them to remain in scope)
M Johan Lindstrom wrote: > At 09:48 2001-12-22 -0600, Mark Wilkinson wrote: > >The solution, apparently, is that the reference to the Menu object must be > >passed back to the main script; apparently the menu-ref is NOT encapsulated > >inside of the Window object that contains it... which is > >counter-intuitive, and > >unlike any other perl module I have ever seen... > > The same goes with Bitmap objects you create, they have to stay in scope > while the bitmap is in use by e.g. a Label control. > > /J > > -------- ------ ---- --- -- -- -- - - - - - > Johan Lindström Sourcerer @ Boss Casinos [EMAIL PROTECTED] > > Latest bookmark: "Design Patterns in Dynamic Programming" > http://www.norvig.com/design-patterns/ > > _______________________________________________ > Perl-Win32-GUI-Users mailing list > Perl-Win32-GUI-Users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users
