From: Andy Wingo <wingo@pobox.com>
To: Jeff Sparkes <jsparkes@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: How to use <gtk-requisition>?
Date: Thu, 28 Apr 2011 12:40:16 +0200 [thread overview]
Message-ID: <m38vuuoe0f.fsf@unquote.localdomain> (raw)
In-Reply-To: <yf3td3k8erv7.fsf@gmail.com> (Jeff Sparkes's message of "Tue, 26 Apr 2011 15:26:36 -0400")
Hi Jeff,
On Tue 26 Apr 2011 21:26, Jeff Sparkes <jsparkes@gmail.com> writes:
> The guile-gnome documentation doesn't explain how to create a
> <gtk-requisition> and I haven't been able to find any examples.
Indeed, it does not appear to be properly wrapped. It is a "boxed"
type, meaning there is a structure behind it, one for which there is a C
declaration but no introspectible definition. If you can rebuild
guile-gnome, you can add a gtk-requisition-new to
gtk/gnome/gw/gtk-support.[ch] and gtk/gnome/defs/overrides/gtk.defs.
Regards,
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2011-04-28 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 19:26 How to use <gtk-requisition>? Jeff Sparkes
2011-04-28 10:40 ` Andy Wingo [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m38vuuoe0f.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-user@gnu.org \
--cc=jsparkes@gmail.com \
/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).