> After the recent discussion about WinScreenLock/WinScreenUnlock for
> double-buffering, I decided to give them a try. Everything worked
> perfectly under Palm OS 3.5 (all ROMS, B/W, Color, Non-Debug, Debug).
> But when I run the application under Palm OS 4.0DR2, the call to
> WinScreenUnlock results in "ScreenMgr.c, Line: 826, unlock out of sync?
> addresses reset too soon". I have made sure that each call to
> WinScreenUnlock is preceded by a call to WinScreenLock, and the number
> of these calls matches.
interesting.. same app?
best way to test it is to just try the switch in your event loop..
you should be able to write something simple:
{
EvtGetEvent(...);
WinScreenLock(winLockDontCare);
// draw to screen
WinScreenUnlock();
}
> Any hints?
the "unlock out of sync? addresses reset too soon" message is
displays under the following condition:
gP->baseAddr == oldHwrBaseAddr
in other words.. the current "screen" visible is the one thats
being written to.. maybe you are switching too fast between the
screens or something?
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.
cheers
// az
[EMAIL PROTECTED]
http://www.ardiri.com/ <--- free games!
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
