caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Berke Durak <berke@altern.org>
To: "Michaël Grünewald" <michael-grunewald@wanadoo.fr>
Cc: caml-list@inria.fr
Subject: [Caml-list] Graphics and Thread (was: Two severe limitations in Graphics module)
Date: Tue, 3 Sep 2002 21:58:55 +0200	[thread overview]
Message-ID: <20020903195855.GA304@gogol> (raw)
In-Reply-To: <878z2pwl4a.fsf@ketanu.dyndns.org>

On Thu, Aug 29, 2002 at 08:55:17PM +0200, Michaël Grünewald wrote:
> Berke Durak <berke@altern.org> writes:
> 
> > On Wed, Aug 28, 2002 at 08:06:42AM +0200, Michaël Grünewald wrote:
> > > 1/You may have two threads, the first will watch the keyboard
> > > (wait_next_event), the second will update puzzle tiles positions, both will
> > > send events to your main loop, that will process these events.
> > 
> > I will try to do this, thanks. I just tried ocamlsdl (I get a weird
> > relocation error at exit) and ocamlsvga (my S3 card isn't fully
> > supported), so I have no other choice.
> 
> This is just an idea :)

Hmm, I've just tried it, it doesn't work, seems that Thread and Graphics
don't mix very well, if one thread calls Graphics.wait_next_event, others
get blocked too. I'm recomping Ocaml with native threads now to see if
that will help !
--
Berke

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


      reply	other threads:[~2002-09-03 19:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-27 20:34 [Caml-list] Two severe limitations in Graphics module Berke Durak
2002-08-28  6:06 ` [Caml-list] " Michaël Grünewald
2002-08-29 11:06   ` Berke Durak
2002-08-29 18:55     ` Michaël Grünewald
2002-09-03 19:58       ` Berke Durak [this message]

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=20020903195855.GA304@gogol \
    --to=berke@altern.org \
    --cc=caml-list@inria.fr \
    --cc=michael-grunewald@wanadoo.fr \
    /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 NNTP newsgroup(s).