No I want to know 'When' it's put in the cradle, not 'if' it's put in the
cradle, and yes, even if I'm not running, so a hack would be in order here
;-)
So, with a re-defined scope, I'll ask again. Which is the most friendly
trap to patch so that I don't do this so often it's burdensome.
-MD
>At 5:54 PM -0800 3/4/99, Matt Disher wrote:
>>In the Hack environment, to avoid patching EventGetEvent, what trap would
>>Palm recommend we patch to trigger a looksie at the batter stats to
>>determine if in fact the Palm V is in the cradle and charging happily ?
>
>I'm confused -- do you want to tell the OS to go check and see if it's
>plugged in? Or do you want to make some call to find out for yourself if
>the device is plugged in?
>
>Anyway, I think SysBatteryInfo, which is documented, will do either of
>those, so there's no need to hack.
>
> --Bob
-----------------------------------------------------------------
Matt Disher 513.583.0707
Fighter Pilot Software, LLC Fax 513.583.0303
3116-C W. Montgomery Rd. #222 eMail: mailto:[EMAIL PROTECTED]
Maineville, OH 45039 web: http://www.fps.com/pilot/
GolfTrac, FPS Utility Pro, HandyCap, & FPS Clock 2 for devices
running the PalmOS (pilot, PalmPilot, PalmIII, WorkPad, etc.)
Custom Programming & Consulting for PalmOS, WinCE, Palm 'sized' CE
