Re: System Events 'not running'
Re: System Events 'not running'
- Subject: Re: System Events 'not running'
- From: DigitEL <email@hidden>
- Date: Sun, 04 Nov 2018 00:57:22 -0700
@Shane/Posters >
Thanks 'cause this confirms to me something I suspected a decade ago...
SystemEvents can start and quit in less than .1 second, which begs the
question... did it ever really launch?... seeing as, again, IMHO it seems to
normally take about 2 seconds to get launched and begin the task I wanted it to
do...
SE is good in enterprise deployment either for multiple task calls or
automation processing... both produce enough activity to keep SE continuously
running with the idea it seems to shutdown upon very short idle... this makes
the more infrequent script use and consistent performance awkward, like tasks
could take 1 second or 1 minute to perform if handed off to SE depending on
other processes running...
Granted... faster processors in recent years have made SE more
'enjoyable' so to speak... but not enough for me...
In retrospect I laud SE for the background processing that does seem to
work well in 'production' environments... but for the one-off, intermittent
usage I try to focus on the Finder/ScriptingAdditions combo and do miss a raft
of functionality that now resides in SE...
You can always try to create a stay-open script that performs some task
with SE and that might keep it running enough for your purpose.
_______
ForNow
EL
> On Nov 2, 2018, at 9:24 PM, Shane Stanley <email@hidden> wrote:
>
>
>
>> On 3 Nov 2018, at 8:44 am, Jacopille, David <email@hidden> wrote:
>>
>> That pushed the problem to System Events, which errored with: “Application
>> System Events isn’t running”.
>
> System Events will quit after a period of inactivity. The default is
> something quite low, so you might want to change it -- see the 'quit delay'
> property.
>
>> So I kill -9 and relaunch System Events.
>>
>> Half the time we still get the “Application System Events isn’t running”
>> after the first kill.
>
> AppleScript is probably caching the reference to the app. Try adding a delay
> after any kill. You might also do better if address System Events by id
> rather than by name.
>
> --
> Shane Stanley <email@hidden>
> <www.macosxautomation.com/applescript/apps/>, <latenightsw.com>
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> AppleScript-Users mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
> Archives: http://lists.apple.com/archives/applescript-users
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden