> This is a cosmetic request and should be lower in priority than issues
> like sound emulation.
What's wrong with sound emulation?
> At least under windows, updating the emulator screen is given VERY low
> priority. So on modern PCs, we have the ironic situation that our code
> runs 5 times faster than normal, yet we didn't see what happened. Also,
> the emulator often misses when it needs to update the screen.
Jeff, you really have this unhelpful habit of throwing out comments without
explaining yourself. What do you mean by the emulating missing when it needs to
update the screen? I know of no problems here. If you are seeing problems,
then you really should report them instead of making allusive remarks about
them.
> When I
> try it on a real device, the whole process runs much slower, but the
> screen update speed is so fast it makes the device looks like a
> supercomputer.
>
> I propose the following "15 minute" solution: Let the user specify a
> frame rate in which the Emulator will update it's current screen
> continuously whether it needs to or not. If you set this to 2 fps, you
> solve the problem of the screen thinking it doesn't need to update.
*If* there is a problem here, then your suggestion is not the right solution for
it, so I don't view this as a reason for adding an FPS throttle.
> If
> you set this to 60 fps and your PC is fast enough, you get Palm-speed
> graphics, along with the bonus of slowing the execution speed itself
> down to closer to real world speeds.
*If* running faster than an actual device is a problem, then your suggestion is
not the right solution for it. So again I don't view this as a reason for
adding an FPS throttle.
-- Keith Rollin
-- Palm OS Emulator engineer
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
