> regarding double buffering in one of my games:
> I got a report that it does flicker and so I rechecked my double 
> buffering code. I used WinScreenLock()/Unlock() and added 
> WinCreateOffScreenWindow() for everything beyond 3.5. Now I even check 
> the return value from WinScreenLock() and use WinCreateOffScreenWindow 
> in case of NULL as return code. But... nevertheless the customer 
> reports flickering on its device. It is a Handspring Visor 3.5H.
> Any comments about this? The emulator doesn't show this flicker, of 
> course.

one of the reasons why we never used WinScreenLock/Unlock() was the
fact that manu licensee's messed up their implementation. these were
mainly sony and handspring who screwed up.

ie: the API didn't work as promised. it was discussed way back in the
forums, search the archives, around early 2001 from memory.

---
Aaron Ardiri                           [EMAIL PROTECTED]
CEO - CTO                                              +46 70 656 1143
Mobile Wizardry                         http://www.mobilewizardry.com/


-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palmos.com/dev/support/forums/

Reply via email to