unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: CDDP 40 - TICE <cddp40.tice@ac-bordeaux.fr>
Cc: Guile user <guile-user@gnu.org>
Subject: Re: C++ application linked with guile dos not quite
Date: 19 Jun 2002 18:42:06 +0200	[thread overview]
Message-ID: <1024504926.28479.32.camel@tice> (raw)
In-Reply-To: <15632.37039.828555.748426@minos.phy.bnl.gov>

Le mer 19/06/2002 à 16:09, Brett Viren a écrit :
> CDDP 40 - TICE writes:
>  > I found another place where it hangs, I never notice it. It apppear also
>  > when the user close a figure without leaving drgenius. I have been able
>  > to trace back:
>  > 
>  > Program received signal SIGINT, Interrupt.
>  > [Switching to Thread 1024 (LWP 27923)]
>  > 0x40802b90 in poll () from /lib/libc.so.6
>  > (gdb) backt
>  > #0  0x40802b90 in poll () from /lib/libc.so.6
>  > #1  0x40622f09 in g_main_is_running () from /usr/lib/libglib-1.2.so.0
>  > #2  0x406228bd in g_get_current_time () from /usr/lib/libglib-1.2.so.0
>  > #3  0x40622c6c in g_main_run () from /usr/lib/libglib-1.2.so.0
>  > #4  0x4035c7f7 in gtk_main () from /usr/lib/libgtk-1.2.so.0
>  > #5  0x0805ae30 in main_prog (argc=1, argv=0xbffffc64) at
>  > drgenius_main.c:124
>  > #6  0x406632d1 in gh_call3 () from /usr/lib/libguile.so.9
>  > #7  0x40666a38 in scm_boot_guile () from /usr/lib/libguile.so.9
>  > #8  0x4068aa13 in scm_internal_lazy_catch () from /usr/lib/libguile.so.9
>  > #9  0x406669e6 in scm_boot_guile () from /usr/lib/libguile.so.9
>  > #10 0x406666e4 in scm_boot_guile () from /usr/lib/libguile.so.9
>  > #11 0x40663304 in gh_enter () from /usr/lib/libguile.so.9
>  > #12 0x0805ae5d in main (argc=1, argv=0xbffffc64) at drgenius_main.c:130
> 
> Are you saying that you want the act of closing the window to cause
> the application to quit?

No this traceback came when a drgenius_view was closed (I use the MDI
feature from Gnome) gnome_mdi_remove_child (mdi, child, FALSE);
And in this case there is no moving windows to be closed, only the main
drgenius window that will stand.



> 
> If so, it sounds to me like you simply didn't connect to the window's
> delete_event.  Eg:
> 
>   your_window_object.delete_event.connect(Gtk::Main::quit.slot());
> 
> (this is for gtkmm 1.2, 2.0 has slightly different syntax).
> 
> -Brett.
> 
> _______________________________________________
> Guile-user mailing list
> Guile-user@gnu.org
> http://mail.gnu.org/mailman/listinfo/guile-user
> 
-- 
Ingénierie Éducative
CDDP des Landes


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user


  reply	other threads:[~2002-06-19 16:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-17 13:24 C++ application linked with guile dos not quite Hilaire Fernandes
2002-06-18  8:25 ` CDDP 40 - TICE
2002-06-18 13:43   ` Brett Viren
2002-06-18 14:37     ` Hilaire Fernandes
2002-06-18 14:45       ` Brett Viren
2002-06-18 17:26     ` Marius Vollmer
2002-06-19  8:02       ` CDDP 40 - TICE
2002-06-19 11:14         ` Marius Vollmer
2002-06-19 13:19           ` CDDP 40 - TICE
2002-06-19 14:09             ` Brett Viren
2002-06-19 16:42               ` CDDP 40 - TICE [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-17 13:23 CDDP

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

  List information: https://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=1024504926.28479.32.camel@tice \
    --to=cddp40.tice@ac-bordeaux.fr \
    --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).