From: Mikael Djurfeldt <mdj@mdj.nada.kth.se>
To: Steve Tell <tell@telltronics.org>
Cc: djurfeldt@nada.kth.se
Subject: Re: select+read on socket in guile,guile-gtk
Date: Thu, 22 Jun 2000 02:19:00 -0000 [thread overview]
Message-ID: <xy766r2vzrw.fsf@mdj.nada.kth.se> (raw)
In-Reply-To: <Pine.LNX.4.21.0006220031560.31348-100000@ariel.lan.telltronics.org>
(Sorry for not having read your messages in detail yet.)
If you want to use GTk in a COOP-threaded application, probably the
best way to do it is to plug in COOP-threads into GLIB. Then you can
run the GTk handler in one thread, but still freely accees GTk from
any thread:
cvs -d :pserver:anoncvs@anoncvs.cygnus.com:/cvs/guile login
cvs -z 9 -d :pserver:anoncvs@anoncvs.cygnus.com:/cvs/guile \
checkout guile/guile-gtkthreads
next prev parent reply other threads:[~2000-06-22 2:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-19 20:17 select+read on socket in gtk,guile-gtk Steve Tell
2000-06-20 21:25 ` select+read on socket in guile,guile-gtk Steve Tell
2000-06-21 21:50 ` Steve Tell
2000-06-22 2:19 ` Mikael Djurfeldt [this message]
2000-06-21 15:27 ` select+read on socket in gtk,guile-gtk Gary Houston
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=xy766r2vzrw.fsf@mdj.nada.kth.se \
--to=mdj@mdj.nada.kth.se \
--cc=djurfeldt@nada.kth.se \
--cc=tell@telltronics.org \
/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).