From: Kevin Ryde <firstname.lastname@example.org>
Date: Fri, 08 Aug 2003 22:43:00 -0000 [thread overview]
Message-ID: <email@example.com> (raw)
I think gdk-colormap-alloc-colors would be better done more in line
with the C function, namely returning a count and a list of #t/#f for
successes and failures.
I also think it should to modify the colour objects it gets to give
back the results from that function. The pixel value in particular is
the whole point of allocating.
* gdk-1.2.defs, gdk-support.c (gdk_colormap_alloc_colors_interp):
Rewrite returning failure count and list of #t/#f, per C function.
Modify given GdkColor objects with results.
Perhaps something in the present style has a place, but if so it
really needs to be under under a different name to avoid confusion. I
presume the current code has never been run though, since it bombs
immediately. (Negatives to scm_done_malloc seem broken, both in guile
1.6 and the cvs).
reply other threads:[~2003-08-08 22:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).