From: Richard <RichardDummyMailbox58407@...>
Date: 2007-05-15T12:40:06+09:00
Subject: Re: sleep 0.2 acts more like sleep 1

Hi Marcin,

> first of all running external program (especially so heavy) is couing that
> delay

I agree that making system calls to Windows is probably the key
culprit.

> easiest (and most ugly) solution would be
> 3.times do |i|
>        Thread.new{system("wv_player.exe", DING)}
>         sleep 0.2i
> end

I agree that threading is a key to getting sub-second responses, if
indeed it's possible with wv_player having to access the file system
three times (I doubt wv-player would cache the selection.)

I tried your introduction of threading,  but it produced the sane
result I've been getting (after removing the "i" at the end of the
sleep statement.)

I outlined in a previous response to you (that was really intended for
Gordon) about what I thought I'd have to do to get sub-second
response.  I also mentioned that I didn't think my application merited
all that work.

Thanks for your response.  I had never looked at threading in Ruby,
so I appreciated giving it a try.

Best wishes,
Richard