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: Fri, 16 May 2003 22:36:00 -0000 [thread overview]
Message-ID: <874r3uplis.fsf@zip.com.au> (raw)
In-Reply-To: <m3u1bvcv43.fsf@lumo.pacujo.net> (Marko Rauhamaa's message of "15 May 2003 22:34:52 -0700")
Marko Rauhamaa <marko@pacujo.net> writes:
>
> The filters need to be protected from GC while they are referred to by a
> GdkWindow. I use user_data to keep track of the filter procedures (as
> well as SCM user data).
Presumably something like the widget signals would be wanted. It'd be
a happy side effect if it meant each distinct gtkwindow was a unique
scheme level object. Good for hashing, comparing, etc.
I'd thought at one stage of proposing an equal? handler for the boxed
types as a similar thing, but ended up doing what I wanted a different
way.
gdkfont has it's own equal function, gdkcolor doesn't need one (on the
pointer value), and gdkcursor seems not unique at the gtk level, so it
was only gdkwindow I was looking at.
> I've tried to be mindful of the process as laid out for me by Marius.
> ("Hack on!", "Make sure it compiles.")
I doubt that's to be taken literally, not if anyone is meant to be
looking at the code. I'm not trying to be critical, just that it'll
be highly advantageous to others interested in the project if you can
better communicate changes you're proposing.
next prev parent reply other threads:[~2003-05-16 22:36 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
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 [this message]
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=874r3uplis.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).