hi all, I have a suddenly failing WinScreenLock(winLockCopy) call and it appears to only fail on Tungsten T and Tungsten T2 devices.
is anyone aware of any factors that would have an impact on this call failing, like code size or anything (no code surrounding this call has changed since it was working)? it even fails on a newly hard reset device with the only 3rd party app being mine (so no memory issues). thanks for any help! patti -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
