This is the mail archive of the
guile-gtk@sources.redhat.com
mailing list for the Guile project.
Re: how to avoid gtk-standalone-main in guile, when developping
- To: David Pirotte <david at altosw dot be>
- Subject: Re: how to avoid gtk-standalone-main in guile, when developping
- From: Joshua Rosen <rozzin at geekspace dot com>
- Date: Fri, 31 Aug 2001 09:13:45 -0400
- CC: "guile-user at gnu dot org" <guile-user at gnu dot org>, guile-gtk <guile-gtk at sourceware dot cygnus dot com>
- References: <3B8E09B3.955D25A6@altosw.be>
David Pirotte wrote:
>
> Hi,
>
> Can someone tell me how another way then gtk-standalone-main
> to launch a gui in guile? this kills the development environment
> when quitting the app ... (a terrible thing, when you have 15 modules
> including postres connection ... and just the latest that you work on
> ...)
>
> Attached is a very simple example that uses gtk-standalone-main: what
> should I do to avoid it (but be abble to 'launch' the gui of course),
> getting error display messages in the guile listener and above all,
> not loosing the environment, whether the gui is bugged, or whether
> I use the quit menu ...
Well, the code defining gtk-standalone-main (in guilegtk 0.19) is:
(define-public (gtk-standalone-main toplevel)
(cond ((gtk-standalone?)
(gtk-signal-connect toplevel "destroy" gtk-exit)
(gtk-main))))