> > no :) you caused the soft-reset when you didn't check that the return > > value was NULL :) > > but i didnt do anything with the returned pointer. as far as i remember i > only locked the screen, did some standard windraw operations and unlocked it > again. some cli�s didn't like that.
of course.. you shouldn't call WinScreenUnlock() if the WinScreenLock() operation failed :) logical? :) those API's are a nightmare to work with, and, quite frankly - they suck. did you know every time you called WinScreenLock() and passed 'copy' as the parameter - it would allocate a new window to store the current window? so, instead of just updating a display pointer - there was an allocation and copying involved.. bad bad bad. but, what would you expect from a palm employee who didn't understand the need for such API's from a gaming perspective? there are so many other ways that API could be written - and, we would have never had the problems we have had by using that API. --- 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/
