I'm having some newb confusion about the timeout value in stream input functions, (read-gesture ...) etc. (read-gesture :timeout 0) always just returns NIL, while timeout values >0 don't seem to have any effect at all. For example, in the Listener (read-gesture :timeout 1) keeps blocking until some gesture is given. Another source of confusion is the :input-wait-handler. From reading the spec I got the idea that it should be called "continously" when there isn't any input in the given stream, but it looks like the function is never executed. Are these real problems or am I just missing something obvious?
tomi.neste@netikka.fi wrote:
I'm having some newb confusion about the timeout value in stream input functions, (read-gesture ...) etc. (read-gesture :timeout 0) always just returns NIL, while timeout values >= 0 don't seem to have any effect at all. For example, in the Listener (read-gesture :timeout 1) keeps blocking until some gesture is given. Another source of confusion is the :input-wait-handler. From reading the =
spec I got the idea that it should be called "continously" when there isn't any input in the given stream, but it looks like the function is never executed. Are these real problems or am I just missing something obvious?
I see the same behaviour as you describe when running under Beagle; I don't know if this is in fact the correct behaviour or if there's a problem in the event processing code.
You are not alone ;-)
-Duncan
mcclim-devel mailing list mcclim-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/mcclim-devel
AFAIK, these basically don't work right now. I briefly hacked on these (toward the goal of fixing scheduled event delivery), and I know there are some obvious things that need to be changed in the SBCL support files. I'll take a look at what I've done (if I can find it..) and see if anything is commitable. I don't know the status of support on the other lisps.
On 5/2/05, Tomi K Neste tomi.neste@netikka.fi wrote:
I'm having some newb confusion about the timeout value in stream input functions, (read-gesture ...) etc. (read-gesture :timeout 0) always just returns NIL, while timeout values >0 don't seem to have any effect at all. For example, in the Listener (read-gesture :timeout 1) keeps blocking until some gesture is given. Another source of confusion is the :input-wait-handler. From reading the spec I got the idea that it should be called "continously" when there isn't any input in the given stream, but it looks like the function is never executed. Are these real problems or am I just missing something obvious?
If there's any test code lying around (Tomi, have any snippets?), I could test this stuff on Allegro. I poked around a little in mp-acl, and it looks like this stuff should work...
R
-
Andy Hefner -
duncan＠robotcat.demon.co.uk -
rpgoldman＠real-time.com -
Tomi K Neste