From: David Pirotte <david@altosw.be>
To: Chris Vine <vine35792468@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: GUI Framework Options
Date: Fri, 12 Oct 2018 14:56:35 -0300 [thread overview]
Message-ID: <20181012145635.46005384@capac> (raw)
In-Reply-To: <20181008235548.453212aa397e9caa9aa74865@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
Hi Chris,
> > > > Is there somewhere a list of all GUI frameworks one can use with Guile
> > > > 2.2.3 or 2.2.4 (I think 2.2.4 is latest stable)?
> > As Mike said, nothing usable at the moment if you 'are looking for and
> > 'absolutely need' GTK3 bindings, but if GTK2 is ok for you, then you may indeed
> > use Guile-Gnome: though it binds (very) old version of GTK2 and some other gnome
> > libs, it is 'rock solid'.
> Not that rock solid. When I last tested it, you still get segfaults with repeated
> insertion and removal of idle timeouts. Did you ever fix that?
No I didn't. I do remember we talked about this, but I can't find the emails we've
exchanged about this, nor could I find a snipset to reproduce it (I must have lost
these emails): with absolutely no promise what so ever, please re-post the short
example you made at the time so we can reproduce it.
Also, patches welcome, I believe you are more competent then myself to track and
solve this one 'nasty' bug - I actually thought you solved this, one way or another
while working on guile-async and guile-async2.
Cheers,
David
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-10-12 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.93.1538928024.28328.guile-user@gnu.org>
2018-10-07 18:53 ` GUI Framework Options Zelphir Kaltstahl
2018-10-08 16:20 ` Mike Gran
2018-10-08 19:12 ` David Pirotte
2018-10-08 21:06 ` Zelphir Kaltstahl
2018-10-08 22:55 ` Chris Vine
2018-10-12 17:56 ` David Pirotte [this message]
2018-10-12 22:38 ` David Pirotte
2018-10-14 11:54 ` Chris Vine
2018-10-08 21:05 ` Zelphir Kaltstahl
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=20181012145635.46005384@capac \
--to=david@altosw.be \
--cc=guile-user@gnu.org \
--cc=vine35792468@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).