public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
To: Marko Rauhamaa <marko@pacujo.net>
Cc: guile-gtk@sources.redhat.com
Subject: Re: Completed GdkWindow; enhanced design
Date: Thu, 15 May 2003 23:19:00 -0000	[thread overview]
Message-ID: <87n0hnhk7x.fsf@zip.com.au> (raw)
In-Reply-To: <m3r870fy1p.fsf@lumo.pacujo.net> (Marko Rauhamaa's message of "15 May 2003 00:50:58 -0700")

Marko Rauhamaa <marko@pacujo.net> writes:
>
>    The GdkWindow user_data is either NULL (initially) or an SCM list.
>    The first element of the list is the SCM user data (or #f). The
>    remainder of the list consists of filter procedures.
>
> You will see that gdk_window_mark will simply return its user_data to
> protect it against GC.

Are you aware that gtk stores a widget (pointer) in the GdkWindow
user_data?  So for instance you can't assume a window obtained from
gtk_widget_window will have an SCM in the user_data field.

The gtk 2 docs suggest one should store only NULL or a widget, because
the gtk event handler will expect that.  The gtk 1.2 code looks like
gtk_main_do_event and gtk_get_event_widget don't attempt any
validation.

(Presumably this issue must have shown up when you tested your
changes, so I wonder if I've badly missed something.)

  reply	other threads:[~2003-05-15 23:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-15  7:59 Marko Rauhamaa
2003-05-15 23:19 ` Kevin Ryde [this message]
2003-05-16  0:58   ` Marko Rauhamaa
2003-05-16  1:23     ` Kevin Ryde
2003-05-16  5:43       ` Marko Rauhamaa
2003-05-16  5:58         ` Marko Rauhamaa
2003-05-16 22:36         ` Kevin Ryde
2003-05-16 22:59           ` Marko Rauhamaa
2003-05-21 13:20           ` first checkin of gnome-guile in guile-gtk CVS Stan Pinte
2003-08-22 23:56 ` gdk-window-set-geometry-hints Kevin Ryde

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=87n0hnhk7x.fsf@zip.com.au \
    --to=user42@zip.com.au \
    --cc=guile-gtk@sources.redhat.com \
    --cc=marko@pacujo.net \
    /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).