Matt, I've only seen it on a real device. Actually, I haven't explicitly tested this on the emulator. But, I'm going to guess it is happening there as well.
Well, I know that I'm not using Evt***AutoOffTimer() APIs. And, you're right...FrmDoDialog doesn't seem to be enough to do it. Even FrmCustomAlert was causing it (or rather, it was not shutting off while the CustomAlert was displayed). But, only in the past few weeks. Prior to that, it was fine. I just don't know what could have changed to affect this. Alarm behavior, and everything else, seems to be functioning as expected. I did, a couple of days ago, find a place that I wasn't unlocking some memHandles...but I fixed those, and it didn't make a difference. (Those, however, were unrelated to the alarms.) Still perplexed. Ryan -------------------- From: Matt Hebley (view other messages by this author) Date: Thu, 5 Jun 2003 15:17:03 ---------------------------------------------------------------------------- ---- You can stop the device going to sleep by playing with the auto off timer. See Evt***AutoOffTimer(). There are several functions that call this internally, but FrmDoDialog should not do this, unless you provide your own event handler and do it yourself. Other than that, I don't know what would cause it. This doesn't help much, but might give you some clues. Does it occur on a real device or just on the emulator? Matt -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
