From: Marius Vollmer <mvo@zagadka.ping.de>
To: Stephen Tell <tell@cs.unc.edu>
Cc: Guile-Gtk List <guile-gtk@sourceware.cygnus.com>
Subject: Re: Converting GdkEvent from C to Guile
Date: Fri, 19 Nov 1999 13:51:00 -0000 [thread overview]
Message-ID: <877ljef8ve.fsf@zagadka.ping.de> (raw)
In-Reply-To: <Pine.GHP.4.10.9911181839520.27875-100000@rukbat.cs.unc.edu>
Stephen Tell <tell@cs.unc.edu> writes:
> Just to make sure I understand Gdk's (undocumented) rules: when I get the
> GdkEvent as an argument to a handler set with gtk_signal_connect(),
> Gdk/Gtk is going to free the event when the handler returns.
Yes, more or less. It just reuses the memory for the next event, in
the normal case.
> So if I let it escape to the guile-gtk world, I set COPYP to TRUE,
> so guile frees its copy when it is done with it.
Correct.
- Marius
prev parent reply other threads:[~1999-11-19 13:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-07 15:47 guile-gtk without dlopen (HP-UX) Stephen Tell
1999-11-08 13:27 ` Marius Vollmer
1999-11-08 19:08 ` Stephen Tell
1999-11-18 13:05 ` Converting GdkEvent from C to Guile Stephen Tell
1999-11-18 15:14 ` Marius Vollmer
1999-11-18 15:50 ` Stephen Tell
1999-11-19 13:51 ` Marius Vollmer [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=877ljef8ve.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=guile-gtk@sourceware.cygnus.com \
--cc=tell@cs.unc.edu \
/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).