The debug roms in the emulator are not reporting anything being corrupted, etc. I did try to cause the problem on the emulator, but I can't make the emulator EVER sleep regardless of my software. Apparently, it is "always on". (Does someone know how to make the emulator actually sleep?) If I could reproduce it on the emulator, perhaps I could get some debugging information if anything is going wrong.
I am handle the SysHandleEvent. Before ever going to my own event handler, I call SysHandleEvent. I'm not sure how that works, however, with a call to FrmDoDialog or FrmCustomAlert. I presume that they implement their own handler in some way. FrmCustomAlert, for example, I do have create any handler for the alert...it is all handled by the system. The only real change that I know I made prior to this starting to happen was that I changed the "type" of the databases I was writing to, and I now set the backup bit on them even though I wasn't before. If there was a problem, however, with the alarm database I have, it should show itself at the time that I add an alarm or review the alarms, since the APIs that I use are identical. I spent more time on this last night, cleared up a couple more issues that I thought might affect it (though, without any real reason why). But, to no avail. Some details that perhaps are useful to know...I have preferences to control how many times to "signal" the alarm with a sound. During the Trigger event, I sound the alarm and then reset the alarm for a few minutes in the future if there are more times to sound the alarm. At the same time, I set the event return parameter such that on the FIRST time it fires, to send the Display event so that I can pop-up the dialog. Subsequent times that the alarm fires, I don't set the display flag so that I don't display the dialog multiple times. Anyhow, I'm still perplexed by this all, so any other tips would be helpful! Ryan ----- Original Message ----- From: Jeff Wheeler <[EMAIL PROTECTED]> Date: Friday, June 6, 2003 8:50 am Subject: RE: Not going to sleep..please help! > 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 > corruptingmemory, 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] > [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'reright...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/
