I agree. This type of routine must be called *each* time your application
gets launched. This will cover you for users running afterburner, and
switching speeds on you between launches etc.
My use of the number 1200 previously was purely an example, and is quite
fictional. I got a number somewhere in this ballpark when running under the
emulator, so who knows what a real device would give...
Regarding the *reason* for this routine.... Err.... I have absolutely no
idea.... Something to do with smart cards.... I just found it an interesting
idea to try and implement.... I'm sure Bill Shaw could elaborate a little
further....
Regards,
Alan Ingleby
Systems Developer
ProfitLink Consulting Pty Ltd
309 Burwood Road
Hawthorn
Victoria 3122
Australia
<[EMAIL PROTECTED]> wrote in message news:42368@palm-dev-forum...
>
>
>
> > I know, but a value of (about) 1200 causes a delay of one tick,
according to
> > the underlying delay loop.
>
> I feel compelled to remind everyone that the given value is highly
platform
> dependent. If you're going to use Alan's technique, then be sure that you
run
> his calibration routine every time your application starts up, rather than
once
> and hardcoding the resulting value (such as 1200). We've got devices
running at
> 16MHz, 20MHz, and 33MHz, each with different RAM wait states. The number
of
> loop iterations will be different for each one.
>
> By the way, I'm curious...what are the reasons and uses for millisecond
timing?
>
> -- Keith Rollin
> -- Palm OS Emulator engineer
>
>
>
>
>
>
> "Alan Ingleby" <[EMAIL PROTECTED]> on 03/14/2001 02:47:11 PM
>
> Please respond to "Palm Developer Forum" <[EMAIL PROTECTED]>
>
> Sent by: "Alan Ingleby" <[EMAIL PROTECTED]>
>
>
> To: "Palm Developer Forum" <[EMAIL PROTECTED]>
> cc: (Keith Rollin/US/PALM)
> Subject: Re: Millisecond delay
>
>
>
> I know, but a value of (about) 1200 causes a delay of one tick, according
to
> the underlying delay loop. It doesn't take too much math to work out
which
> value would cause a delay of 1 ms. i.e.: If TicksPerSecond = 100,
> millisecond delay is 120, if TicksPerSecond is 60, millisecond delay = 72.
>
> Regards,
>
> Alan Ingleby
> Systems Developer
> ProfitLink Consulting Pty Ltd
> 309 Burwood Road
> Hawthorn
> Victoria 3122
> Australia
> "HowY" <[EMAIL PROTECTED]> wrote in message
> news:42297@palm-dev-forum...
> >
> > But a tick is 1/100th of a second...
> >
> > not a millisecond....
> >
>
>
>
>
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
