[wxruby-users] alternative to destroying a dialog? (to avoid segfault)
Doug Glidden
lists at ruby-forum.com
Sat Sep 13 00:43:53 EDT 2008
Alex Fenton wrote:
> Hi
[snip]
> 1) Your app consists of one or more frames, with dialogs shown at
> various times for particular actions. This is the much commoner case.
>
> For this, the Dialogs should have the appropriate Frame parent as the
> first argument to the constructor, not nil. They'll then be cleaned up
> when the dialog is closed - no need to call destroy to exit cleanly.
>
[snip]
>
> alex
This is what I ended up doing. Actually, the dialog (a series of
dialogs, actually) is displayed prior to the main window of the app
being displayed. The way I originally had the app set up, I couldn't
set the window to be the parent of the dialogs because it didn't exist
yet, but I moved some things around so that the window can be the parent
even though it hasn't been displayed yet.
Thanks for the reply,
Doug
--
Posted via http://www.ruby-forum.com/.
More information about the wxruby-users
mailing list