public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <3B8F8D89.CF95BB3A@geekspace.com> (raw)
In-Reply-To: <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))))

      parent reply	other threads:[~2001-08-31  6:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-30  3:26 David Pirotte
2001-08-31  1:57 ` Neil Jerram
2001-08-31  4:01   ` David Pirotte
     [not found]     ` <999269215.1502.15.camel@soleil>
2001-09-01  4:57       ` David Pirotte
2001-08-31  6:16 ` Joshua Rosen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3B8F8D89.CF95BB3A@geekspace.com \
    --to=rozzin@geekspace.com \
    --cc=david@altosw.be \
    --cc=guile-gtk@sourceware.cygnus.com \
    --cc=guile-user@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).