From mboxrd@z Thu Jan  1 00:00:00 1970
From: Joshua Rosen <rozzin@geekspace.com>
To: David Pirotte <david@altosw.be>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>, guile-gtk <guile-gtk@sourceware.cygnus.com>
Subject: Re: how to avoid gtk-standalone-main in guile, when developping
Date: Fri, 31 Aug 2001 06:16:00 -0000
Message-id: <3B8F8D89.CF95BB3A@geekspace.com>
References: <3B8E09B3.955D25A6@altosw.be>
X-SW-Source: 2001-q3/msg00037.html

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))))