This has something to do with calling WinScreenLock and WinScreenUnlock. WinScreenUnlock is finding that the lock count has reached zero and that it's time to draw the buffered changes. However, it's also seeing indications that this buffer flushing has already taken place. That's why it says "unlock out of sync".
If you're not explicitly calling WinScreenLock and WinScreenUnlock in your application, I'm not sure what else could lead to this problem -- Keith At 2:14 PM -0700 4/19/02, Edward P. Ross wrote: >When running my application on the IIc Color Debug ROM (OS 3.5) I have >no errors. I can run a million gremlin events with no problem. > >When I loaded my app into the PalmOS4.0-EN-Color-Debug ROM and run the >app, I get an error that says "program called SysFatalAlert with the >message: "ScreenMGr.c, Line: 828, unlock out of sync? addresses reset >too soon". > >Here's the weird part - if I run the program in Codewarrior and debug it > >with the same ROM, I never get the error. > >I am not lockign the screen anywhere and can't find anything in the >database regarding this. > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
