From: tomas@fabula.de
Subject: Questions about guile-gtk
Date: Wed, 16 Oct 2002 13:48:48 +0200 [thread overview]
Message-ID: <20021016114848.GB6292@www> (raw)
Hi, experts
(yeah, Marius, I fear that's especially you ;-)
while trying to come up with bindings for the GtkCanvas widget
(see my other posting), I came across several questions. Maybe
someone can shec a bit of light on me.
- I use the function sgtk_build_args(), which, as I understand,
tries to convert an SCM keyword list into a GtkArg array to
set the properties of a Gtk object.
The third argument to it is a `protector', I don't understand
exactly its use (but it's usually passed the object, which is
annoying if it's the object just being created ;-)
What I'm supposed to do with this?
- I can't draw a line. The problem is that one of the parameters
needed is a GtkCanvasPoints* (which is not a regular Gtk object,
but just a C structure). Does the guile-gtk conversion mechanism
provide a way to cope with that, or have I to do something
by hand here?
- How do I handle C functions with in/out parameters, that is,
pointers, like:
gtk_canvas_get_scroll_region(GtcCanvas c,
double *x1, double *y1,
double *x2, double *y2)
Again: is there something in guile-gtk to cope with it and didn't
I see it, or is it ``roll your own''?
Besides, I think another discussion is in order: is it worth extending
the binding mechanism of guile-gtk (I actually like it), or should we
move towards a more general approach (g-wrap or swig)?
In the mid-term I think it's important to have an ``official'' bindings
generator tool, just to attract good bindings...
Thanks for any input
-- tomas
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2002-10-16 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 11:48 tomas [this message]
2002-10-19 14:07 ` Questions about guile-gtk Marius Vollmer
2002-10-19 14:21 ` Marius Vollmer
2002-10-21 10:41 ` tomas
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=20021016114848.GB6292@www \
--to=tomas@fabula.de \
/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).