From: "Greg J. Badros" <gjb@cs.washington.edu>
To: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-gtk@sourceware.cygnus.com
Subject: Re: gtk-clist-append does not work with shared substrings
Date: Thu, 20 Jan 2000 21:22:00 -0000 [thread overview]
Message-ID: <qrrd7qwxrrd.fsf@clavicle.cs.washington.edu> (raw)
In-Reply-To: <87ogagbb8l.fsf@zagadka.ping.de>
Marius Vollmer <mvo@zagadka.ping.de> writes:
> "Greg J. Badros" <gjb@cs.washington.edu> writes:
>
> > That's the same as mine. I get the same *responses* as you, but the
> > CLIST is not populated with the correct strings. Try this:
>
> Ahh, I see. There are two bugs in guile-gtk that prevent it from
> working. The first is that no automatic type conversion used for
> composite objects (including the one that takes substrings to normal
> strings), and the second is that guile-gtk accepts substrings as valid
> types but can't deal with them then.
>
> I have fixed the second bug, so now your example will produce a "Wrong
> type argument" error. The first bug needs more work and more thought,
> because of memory management issues and of mode `out' parameters. You
> can work around the first bug by explicitely using string-copy to get
> from a substring to an equal normal string.
Right, that's roughly what I did in Scwm's gtk-table-display.scm.
Fixing the first problem definitely is helpful as it's better than just
failing silently.
> My current thinking is to convert a composite of mode `in' by copying
> it, and one of mode `out' or `inout' by modifying it in place. Any
> thoughts about this?
I've never achieved a deep understanding of the guile-gtk interface
description stuff, but my naive take on this stuff is that that would be
sufficient. You definitely don't want to side-effect an in parameter.
> > Right-- I may care about which GTk+, but I'm more likely to care about
> > which guile-gtk. We need both, and only the former is available.
>
> You can now use gtkconf-guile-gtk-version to get at the guile-gtk
> version. gtkconf-version will now reflect the version of Gtk+ that is
> actually active.
Great, thanks!
Greg
next prev parent reply other threads:[~2000-01-20 21:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-16 15:19 Greg J. Badros
2000-01-19 11:10 ` Marius Vollmer
2000-01-19 11:37 ` Greg J. Badros
2000-01-20 22:13 ` Marius Vollmer
2000-01-20 21:22 ` Greg J. Badros [this message]
2000-01-23 8:04 ` Marius Vollmer
2000-01-23 9:26 ` Greg J. Badros
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=qrrd7qwxrrd.fsf@clavicle.cs.washington.edu \
--to=gjb@cs.washington.edu \
--cc=guile-gtk@sourceware.cygnus.com \
--cc=mvo@zagadka.ping.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).