On Thu, Jan 30, 2003 at 01:50:17PM +0100, Aaron Ardiri wrote:
> of course.. you shouldn't call WinScreenUnlock() if the WinScreenLock()
> operation failed :) logical? :)
Yes! It's logical because if WinScreenLock() failed, then the screen
isn't locked and doesn't need unlocking. It's a very common idiom:
don't call fclose() if fopen() failed; don't call free() if malloc()
failed; etc, etc.
> those API's are a nightmare to work with, and, quite frankly - they
> suck.
But nonetheless I'm sure you're right and they're a nightmare to work
with for lots of other reasons :-).
John
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
