I don't have any specific advice for how your code is causing this behavior, but from your descriptions, it appears that you've recently added something "unrelated" that is resulting in the problem. Perhaps you are corrupting memory, perhaps you corrupt a program pointer and run rogue code, etc.
Have you tried using your source code control system to check out "old" versions of your code in order to verify that the problem doesn't occur? Then roll changes back in until it occurs again. This may give you a clue. If you don't use source code control, perhaps you can simplify your program by conditionally compiling out whole sections of features and code until the problem stops occurring. Jeff -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ryan Bruner Sent: Thursday, June 05, 2003 8:28 PM To: Palm Developer Forum Subject: Re: Not going to sleep..please help! 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 -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
