Open GoogleCodeExporter opened 8 years ago
you could fix that with a conditional apple script ie something like "if
ScreenSaverEngine process not running Running" you may have too look nto that
as i
have little to no experience with applescript
Original comment by Jackom...@gmail.com
on 19 Jul 2009 at 7:11
This also happens with "in" scripts on 10.6.1 with a Nokia 6120 Classic and
Proximity 1.5.
That may be intentional (I don't know?) but I'd think it wasn't?
I'd create a new issue, but I'm not sure it is one?
Original comment by soren.an...@gmail.com
on 24 Sep 2009 at 6:01
Just a thought, but what about adding the option to only fire the script when
the
status has proximity has changed from the previous scan. So, for example, if
the
phone is currently 'out of range', time elapses, Proximity scans again and
finds the
same, script doesn't fire.
Original comment by tomwy...@gmail.com
on 8 Oct 2009 at 10:37
Original issue reported on code.google.com by
thraxisp...@gmail.com
on 30 Jun 2009 at 1:40