> IMO, I think it's probably more sensible (at this stage in
> time) to look
> upon the 18.2Hz tick as a fundamental constraint to build DHTML games
> around, rather than try to fix the whole platform via
> multiple threads.
I think it's the only possibility. The setInterval is the javascript timer,
not
the system timer that the browser works in/on/with. Even if you use
multi threading you keep running in to the problem I mentioned: if the
browser
can't render and parse the javascript within 1 timerinterval...etc.
Also note that I noticed that the latest Mozilla is rendering stuff at a
more
smooth and faster way then previous versions or IE versions.
..just hoping that browser developers will optimise their rendering code.
Pascal Bestebroer ([EMAIL PROTECTED])
Software ontwikkelaar
Oberon Informatiesystemen b.v.
http://www.oibv.com
_______________________________________________
Dynapi-Help mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-help
