User Tools

Site Tools


trigger:Application

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
trigger:Application [2019/07/01 01:35]
peternlewis [Topics]
trigger:Application [2020/11/01 21:25]
peternlewis
Line 5: Line 5:
 * Launches. * Launches.
 * Quits. * Quits.
-Periodically ​while the application is running.+Is Running (and periodically ​while it remains ​running).
 * Activates. * Activates.
 * Deactivates. * Deactivates.
-Periodically ​while the application is at the front.+Is Active (and periodically ​while it remains ​at the front).
  
 An application Activates when it comes to the foreground, and deactivates when another application comes to the foreground. An application Activates when it comes to the foreground, and deactivates when another application comes to the foreground.
 +
 +The `Is Running` and `Is Active` variant will trigger once when the application first launches/​activates,​ and then periodically thereafter while the application continues to run/remains at the front.
  
 You could use a trigger like this to simulate workspaces by automatically setting up an application the way you want when you launch it, or you could clean up after an application when you quit. You could use a trigger like this to simulate workspaces by automatically setting up an application the way you want when you launch it, or you could clean up after an application when you quit.
Line 16: Line 18:
 You can use the [[token:​TriggerValue|%TriggerValue% Text Token]] to determine the path of the application (previous to 9.0, the `%TriggerValue%` token contained the name of the application). You can use the [[token:​TriggerValue|%TriggerValue% Text Token]] to determine the path of the application (previous to 9.0, the `%TriggerValue%` token contained the name of the application).
  
-If a macro that is triggered by Acorn launching is in a macro group that is active only when Acorn is running, then the trigger will probably never fire since the macro will be inactive until after the event has passed. ​ As such, macros that are triggered by as application trigger should be in a macro group that is always active (or at least, a macro group that is active both before and after the event happens).+(!) If a macro that is triggered by an application ​launching is in a macro group that is active only when that application ​is running ​or active, then the trigger will probably never fire since the macro will be inactive until after the event has passed. ​ As such, macros that are triggered by as application trigger should be in a macro group that is always active (or at least, a macro group that is active both before and after the event happens).
  
 ===== See Also ===== ===== See Also =====
Line 34: Line 36:
 * [[token:​ApplicationPath|%ApplicationPath%]] token * [[token:​ApplicationPath|%ApplicationPath%]] token
 * [[token:​ApplicationBundleID|%ApplicationBundleID%]] token * [[token:​ApplicationBundleID|%ApplicationBundleID%]] token
 +* [[token:​Trigger|%Trigger%]]
 +* [[token:​TriggerBase|%TriggerBase%]]
 +* [[token:​TriggerValue|%TriggerValue%]]
 * [[:​Tokens|See all Tokens]] * [[:​Tokens|See all Tokens]]
- 
-==== Topics ==== 
- 
-* [[:​Frequently Asked Questions|FAQ]] 
  
 === Triggers === === Triggers ===
trigger/Application.txt ยท Last modified: 2020/11/01 21:25 by peternlewis