From: Eric@pretzelnet.org, Gillespie@pretzelnet.org, Jr. <epg@pretzelnet.org>
To: guile-gtk@sources.redhat.com
Subject: Guile's libglade vs. Python's (was Re: [OT?] libglade, guile-gtk and glade-xml-signal-autoconnect)
Date: Tue, 05 Feb 2002 10:44:00 -0000 [thread overview]
Message-ID: <m2ofj322gy.fsf_-_@argo.pretzelnet.org> (raw)
In-Reply-To: <1012408302.1300.129.camel@flophouse> (Bill Gribble's message of "30 Jan 2002 10:31:41 -0600")
(I'm posting this to guile-gtk on a hunch that this is the right place
to discuss the Guile libglade bindings; i couldn't find any
guile-libglade list).
Bill Gribble <grib@linuxdevel.com> writes:
> It would be nice to have a way to specify that the function name
> is Scheme rather than C. Since libglade seems to silently drop
> things that don't map to C functions, you could have a naming
> convention that signal handlers starting with scm: are treated
> as Scheme functions and invoked via a wrapper. autoconnect
> could be wrapped with a little test that makes those
> connections.
And in a later message:
> That's what I'm saying. glade-xml-signal-autoconnect is just a
> wrapper that calls glade_xml_signal_autoconnect, which means
> that only C function bindings are looked for.
The wrapper is what the Python bindings do, i think. Having
autoconnect not working like the user expects is probably a bad idea.
Can this be fixed in a future release? Maybe i'll find the time to
make a patch...
--
Eric Gillespie, Jr. <*> epg@pretzelnet.org
"When everyone has to reinvent the wheel, many people invent
square wheels."
parent reply other threads:[~2002-02-05 18:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1012408302.1300.129.camel@flophouse>]
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=m2ofj322gy.fsf_-_@argo.pretzelnet.org \
--to=eric@pretzelnet.org \
--cc=Gillespie@pretzelnet.org \
--cc=epg@pretzelnet.org \
--cc=guile-gtk@sources.redhat.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).