There's a simple explanation for what you've been observing: The sleep process
has been changed somewhat.
When an autoOffChr or hardPwrChr get to SysHandleEvent, they are now turned into
a powerOffChr, which
(once it gets to SysHandleEvent again) actually causes the device to go to
sleep. Note that
hardPwrChr can also be turned into a backlightChr if the power key is held down
for a couple seconds.
Hope this helps...
Jesse
Bastian <[EMAIL PROTECTED]> on 09/27/99 12:54:35 PM
Please respond to [EMAIL PROTECTED]
Sent by: Bastian <[EMAIL PROTECTED]>
To: Palm Dev Mailing List <[EMAIL PROTECTED]>
cc: (Jesse Donaldson/HQ/3Com)
Subject: Button behavoir difference on Palm V / Palm VII
Hi List,
I have to detect keydown event from an EventPatch.
On the Palm V I see the following behavoir:
0) Palm V is running ...
1) Physical power key pressed (aka turn off)
2) I pass the keyDownEvent (hardPowerChr) to SysHandleEvent
3) Palm goes to sleep. SysHandleEvent not returned yet.
4) Physical power key pressed (aka turn on)
5) SysHandleEvent now returning.
6) ...
with Palm VII, SysHandleEvent is allways returning, though the device
goes to sleep.
Any idea how the behavior in this regard on the Palm VII is?
Or where I can get more information in this issue?
Thanks
Bastian
