Difference between revisions of "Trigger: Shortcut Launched"

m
 
Line 1: Line 1:
<pre style="background-color: #EEEEEE; color: Black; border-radius: 10px; padding: 10px;">
+
<pre style="background-color: #ACC8E5; color: #112A46; border-radius: 10px; padding: 10px;">
 
This trigger was originally used to expose a macro to be available to other apps that are able to launch Android shortcuts.
 
This trigger was originally used to expose a macro to be available to other apps that are able to launch Android shortcuts.
  
Line 6: Line 6:
 
For macros that are only designed to be invoked from Android shortcuts it still makes sense to use this trigger to make it clear this is the intended use.
 
For macros that are only designed to be invoked from Android shortcuts it still makes sense to use this trigger to make it clear this is the intended use.
 
</pre>
 
</pre>
<br>
 
'''Example Usage'''<br/>
 
 
<pre style="background-color: #AC2424; color: white; border-radius: 10px; padding: 10px;">
 
Triggers
 
 
 
</pre><br>
 
<pre style="background-color: #1665B0; color: white; border-radius: 10px; padding: 10px;">
 
Actions
 
 
 
</pre><br>
 
<pre style="background-color: green; color: white; border-radius: 10px; padding: 10px;">
 
Constraints
 
 
 
</pre><br>
 
<pre style="background-color: teal; color: white; border-radius: 10px; padding: 10px;">
 
Local variables
 
 
 
</pre><br>
 

Latest revision as of 18:45, 23 January 2024

This trigger was originally used to expose a macro to be available to other apps that are able to launch Android shortcuts.

It is now possible to select from any macro for an Android shortcut regardless of what triggers are configured, therefore this trigger is now not necessary and really equivalent to the empty trigger. 

For macros that are only designed to be invoked from Android shortcuts it still makes sense to use this trigger to make it clear this is the intended use.