A friend of mine has a Palm V and we experimented with the up/down buttons
turning off alarms. It turned out to be a DatebookIII problem. After doing a hard
reset, we used the original Datebook without problems.
bryon
*********** REPLY SEPARATOR ***********
On 4/29/99 at 4:54 PM Petr Bajer wrote:
>>Another possible clue: Clock III also has a Stopwatch function that uses
>>the Date Book, Address Book, To Do List and Memo Pad keys as Start,
>>Lap/Split, Reset and Stop buttons, respectively. When the Stopwatch is
>>running, it does not doze between event retrievals - i.e., it uses the call
>>EvtGetEvent(&fEvent,0). It looks for a fEvent.data.keyDown.chr value in the
>>0x204 to 0x207 range to indicate that a button has been pushed. On units
>>where the wakeup bug is present, pressing the buttons does not work - i.e.,
>>Clock III never receives an event with a fEvent.data.keyDown.chr value in
>>the specified range. Looking first at aspects of the Dragonball EZ that
>>could cause both of these symptoms might save some time.
>
>
>
>Interesting! Beside having a lot of complaints about alarms we also have a
>lot e-mails from PalmV users complaining that hardware buttons do not work
>in another app of ours which uses hard buttons extensively. HotSync(R) :-)
>cures this problem. We have never figured out what was going on and did not
>connect these two problems together .
>
>The behaviour they describe is exactly what would happen if there were
>missing keyDown events! This reminds me the very old story of PalmPilot
>Personal never sending the autoOffChr. I complained several times but nobody
>believed me. I still have the unit that does not send the autoOffChr and can
>send the ROM file to someone if there is any interest.
>
>Regards,
>Petr
-------------------------------------------------------------
Did you get your bonus check?, visit http://www.grey-net.com/
Need Hits? Get over 3 million for free.
http://www.freeyellow.com/members7/ropeman/
