Daniel McCarty wrote:
> 
> Matt Disher wrote:
> >
> > 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.
> 
>    SysBatteryInfo would seem like the best idea.  Just check the
> pluggedIn parameter (I'm assuming you're doing this from a hack).

   Sometimes my "best ideas" aren't so good.  ;)  If you're trying
to do this from a hack, it might be better to trap HwrPluggedIn()
instead.

Regards,
Daniel.




Reply via email to