this would mean system.currenttimemillis is using windows timers, the
worst choice available on windows.
a better choice would be the multimedia timers.
perhaps the right folk could be pointed out, so this could be addressed?
> -----Original Message-----
> From: Fred Klingener [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 10, 2001 8:41 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [JAVA3D] fps needed.
>
>
> From: "Yazel, David J." <[EMAIL PROTECTED]>
> Sent: Tuesday, July 10, 2001 8:30 AM
>
>
> > ...
> > Note that under windows the lowest granularity of
> System.currentTimeMillis()
> > is 55 ms, which is abysmal and inappropriate for animation.
> > ...
>
> Probably true for W95, W98, WMe, etc., and highly unreliable at
> that. WNT and W2k seem to have a pretty stable granularity of
> 15 or so milliseconds - workable for animations if you feel it's
> absolutely necessary to build your own simulation clock.
>
> Kinda erodes that 'run anywhere' thing, though.
>
> Cheers,
> Fred Klingener
>
> ==============================================================
> =============
> To unsubscribe, send email to [EMAIL PROTECTED] and
> include in the body
> of the message "signoff JAVA3D-INTEREST". For general help,
> send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
>
==========================================================================To
unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
