caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Michaël Grünewald" <michael-grunewald@wanadoo.fr>
To: caml-list@inria.fr
Subject: [Caml-list] Re: Two severe limitations in Graphics module
Date: 28 Aug 2002 08:06:42 +0200	[thread overview]
Message-ID: <87u1lfikjx.fsf@ketanu.dyndns.org> (raw)
In-Reply-To: <20020827203437.GA326@gogol>

Berke Durak <berke@altern.org> writes:

> Hello everyone,
> 
> I was wondering how many hours would coding Tetris using the Graphics
> module require when I noticed that the Graphics module lacks two
> important constructs :
> 
> 1) The Graphics.wait_next_event doesn't allow you to wait for an event
> with a timeout, à la select(). Since in Tetris things might happen
> even if you don't press any key, you can't wait indefinitely.
> 
> Workarounds include :
> 	-- continuously calling wait_next_event [Poll;...]  and doing a
> small delay between each call. I think I will do this. Not very
> efficient, since the delay must be of the order of the screen refresh
> interval.
> 	-- do a horrible hack by getting the X11 file descriptor -- but
> then how will Microsoft-sequestrated people enjoy your delightful
> MLtris ?

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.

2/Why don't use alarm signam or something like ?

> 2) There is no way to get the cursor keys. Sure that's no problem to
> h,j,k,l-people. Might I suggest the following bindings :
> 
> 	-- left : '\002' (Ctrl-b)
> 	-- right : '\006' (Ctrl-f)
> 	-- up : '\011' (Ctrl-k)
> 	-- down : '\010' (Ctrl-j)
> 
> or a supplementary keysym type like
> 
> 	type keysym = Latin1 of char | Left | Right | Up | Down | ...
> 
> 3) It would further be nice to be able to select() another FD plus
> the graphical interface, portably if possible. I know, under UNIX,
> simply adding a function to the Graphics module that returns the
> descriptor of the X11 connection would solve problems 1 and 3.
> That would be non portable.
> 
> Has anyone managed to solve these issues cleanly (i.e. without
> patching the compiler) ?
> --
> 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
> 

-- 
Michaël Grünewald <michael-grunewald@wanadoo.fr>  - RSA PGP Key ID: 0x20D90C12
-------------------
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-08-28 20:54 UTC|newest]

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

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=87u1lfikjx.fsf@ketanu.dyndns.org \
    --to=michael-grunewald@wanadoo.fr \
    --cc=caml-list@inria.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).