I've noticed this when you do a hard reset. The "Erase all data? YES - up
button" screen" drives my system to a crawl.
I'm sure it's just a poorly written tight loop in the emulator.
If you write a windows program like this
int APIENTRY WinMain(HINSTANCE hInstance,
HINSTANCE hPrevInstance,
LPSTR lpCmdLine,
int nCmdShow)
{
while (true)
NULL;
return 0;
}
All your CPU cycles will be eaten up.
A well written app will not do anything if it has nothing in the queue, like
this
while (GetMessage(&msg, NULL, 0, 0))
{
}
GetMessage doesn't return unless there is a relavent message, so it lets the
system do its thing when the app is idle.
In some cases the emulator appears to just do a tight loop.
"Dan Patrutiu" <[EMAIL PROTECTED]> wrote in message
news:111218@palm-dev-forum...
>
> When I run the Emulator and the Launcher window is shown, all things
are
> normal, the processor time taken by the Emulator is non-semnificative. But
> when I run some programs, including the one I develop, the System Idle
> process has 0 percents of the processor time, and the Emulator 99
percents.
> This is not happening to all the programs, and I am very curious
just to
> know the reason for this. ( maybe the Emulator is having some problems and
> is cycling up all the time )
>
>
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
