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: Added a bunch of GDK routines.
Date: Sun, 11 May 2003 23:28:00 -0000	[thread overview]
Message-ID: <878ytd5ai8.fsf@zip.com.au> (raw)
In-Reply-To: <m33cjyxi3p.fsf@lumo.pacujo.net>

Marko Rauhamaa <marko@pacujo.net> writes:
>
>    * gdk_gc_new_with_values (because the individual field setters and
>      gdk_gc_new are fully sufficient and convenient).

Personally I'd found individual set calls a bit tedious, and instead
made myself a keyword version, eg.

    (c-gdk-gc-new-with-attrs (gtk-widget-window draw)
			      #:foreground      cross-colour
			      #:exposures       #f
			      #:line-attributes '(1 on-off-dash butt miter))
  
I think the individual calls get combined at the X level, so I guess
there's nothing lost by not having a with_values variant.

GdkGCValues might still have a use for gtk_gc_get, though I don't know
whether that function can be made to work.  I guess the GdkGC returned
would have to know to call gtk_gc_release.

>  - guile-gtk.[ch]: Made xmalloc and xrealloc non-static

Might be prudent to rename them to sgtk_something.

I guess it might be nice to use scm_malloc to gc if out of memory, but
I'm not smart enough to know if that'd cause subtle problems.

  reply	other threads:[~2003-05-11 23:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-02  1:25 Marko Rauhamaa
2003-05-11 23:28 ` Kevin Ryde [this message]
2003-05-12 18:06   ` Marko Rauhamaa
2003-05-12 18:56     ` Marko Rauhamaa
2003-06-06 22:23 ` GdkWChar (was: Added a bunch of GDK routines.) Kevin Ryde
2003-06-14 23:58 ` gdk-gc-copy comments " Kevin Ryde
2003-06-20 23:54 ` sgtk_timestamp returns " 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=878ytd5ai8.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).