Daniel,
You are absolutely correct, winNT and Win2K both
have a minimum timeslice of 10 ms and under IE will
default to multiples of that amount. Under NS, any
number above that minimum will closely execute.
According to the results we are getting back, Opera
also defaults to multiples of the minimum timeslice
under mac platforms but appears to closely reflect the
setting under win (this needs verifying).
Results so far (please verify these if you have these
systems)
Minimum timeslices:
win9x 55 ms
winME 55 ms
winNT 10 ms
win2K 10 ms
Linux 1 ms (need verification)
mac 2.75 ms (based on test multiples, need more
data here, I suspect differences in different mac
platforms and I am "Mac" ignorant, if someone could
teach me I would be greatful)
Your timing correction code for animations looks good.
But on our slower win9x systems, I suspect it will
create very "jumpy" animation. I will add this code
as an option under the animation timing example
tonight and we can all compare and report back.
However, it is "fantastic" for those developers who
want to use the setTimeout to do timeline scripts. I
prefer using the events method at this time as I am
more interested in how smooth it plays back (yes, I do
program in Flash, but it is not compatible with other
elements on the screen. It makes fantastic animated
insets - ducking rocks before they are thrown).
Cheers,
Dave C. "You Changed What?!?"
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
