While not being an Apple Script expert, I am under the impression that every time the caller/its parent process's fingerprint changes one needs to allow it to call System Events (again).
That does not seem to be necessary with display notification.
And as this also got a parameter for sound that might be the better approach?
While not being an Apple Script expert, I am under the impression that every time the caller/its parent process's fingerprint changes one needs to allow it to call
System Events
(again).That does not seem to be necessary with
display notification
. And as this also got a parameter forsound
that might be the better approach?Regarding backwards compatibility: this is mentioned in some doc from Apple that dates back by at least 6 years. So I assume this should cover all scenarios: https://developer.apple.com/library/archive/documentation/LanguagesUtilities/Conceptual/MacAutomationScriptingGuide/DisplayNotifications.html
WDYT?