Hi!
> the "unlock out of sync? addresses reset too soon" message is
> for WinScreenUnlock() to function correctly, the current visible
> screen must NOT be the screen that you are drawing to. otherwise
> you get this error. it is a non-fatal display, and it could be a
> bug of 4.0 - but it shouldn't happen on a real device.
>
> i didn't think they changed much code from 3.5 -> 4.0 dealing with
> the screen code :)) surely nothing that would break what you are
> doing.
I did some more research on this topic, and it turned out to be a problem that only
happens on POSE with the 4.0 VZ ROM and the VZ
device. On this particular configuration, WinScreenLock returns NULL to indicate that
it failed, and WinScreenUnlock then throws the
"unlock out of sync" message.
The bad thing is: I also found some code that uses this particular test (checking for
NULL return value with WinScreenLock) to
detect that it is running on a monochrome Sony Clie, which is also what Red Mercury
Software observed for their Atom Smasher game.
Red Mercury also released a special Visor Prism version because of the same problem.
So that could mean there are actually two
existing OS 3.5 devices out there, where this problem exists in the real world :-((((
Right now, I am doing a fake WinScreenLock(winDontCare) just to check the return value
and then set my function pointers either to a
version using WinScreenLock, or one which is doing smart copying from an offscreen
buffer to the LCD screen. The smart copying
routine is also used for pre-3.5 devices.
Cheers,
Tilo
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
