I didn't reply before, because I know I've addressed it many times
before. However, the only thing I could find in our stellar archives
searching for "tick" or "TimGetTicks" was:
http://www.escribe.com/computing/pcpqa/m5135.html
While still true, you may not have believed it, since it was posted a
while ago.
But, in short, the answer is that the rate at which ticks advance is
dependent on the speed of the host computer and what operations the
emulated code is performing.
Trying to get the emulated tick counter to increment 100 times per
second is problematic. For one thing, it's difficult to get that
kind of resolution out of the host computer. That is, how does Poser
know that 10 msecs has elapsed? And for another thing, how can Poser
make that determination in a way that doesn't slow down emulation?
All my previous attempts to get ticks to increment at a sane pace
have led to serious emulation speed slowdowns. And finally, the two
places in the OS where the tickcount is stored (yes, it's stored in
two places) are undefined, making Poser's task of updating it and
keeping it updated in the face of the OS's own attempts to update it
that much harder.
-- Keith Rollin
-- Palm OS Emulator engineer
At 1:02 PM -0400 6/22/01, Paul Nevai wrote:
>I reported this to a couple of places but rec'd no feed back...
>
>I noticed that POSE 3.2 on the Mac has significantly slowed down. As if the
>internal clock was slowed down. For instance, this code
>
> startedTicks = TimGetTicks ();
> while (TimGetTicks () < startedTicks + 100)
> {continue;}
>
>takes about 5 secs. Am I the only one with this problem?
--
-- Keith Rollin
-- Palm OS Emulator engineer
P.S. Check out the new e-mail address. [EMAIL PROTECTED] will work
for a while, but anyone mailing me needs to update to the new one
eventually.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
