Fulltext results:
- appcreation @tasker:docs:en
- ello World Example</A> <LI><A HREF="#config">App Configuration</A> <LI><A HREF="#sign">Signing</A> <LI><A HREF... lo World popup! </P> <A NAME="config" /> <H3>App Configuration</H3> <P>More usually, before an app is generated you will be presented with a configuration screen which lets you specify various options for... , the <B>Minimum Android Version</B> in the child Configuration screen must be set to <B>16</B> or higher. If sup
- ah_index @tasker:docs:en:help
- Data</H4>Dynamically load a task into the active configuration or replace the whole active configuration.<br/><br/>Usually the data to be loaded is first read into a variable via the Read File action.<br/><br/>When a new configuration is successfully loaded, the task (and all others)... k.<br/><br/>Warning: data you enter in the plugin configuration screen is collected by the *plugin*, not by Taske
- activity_widget_configure @tasker:docs:en
- ure</TITLE></HEAD> <BODY> <H2> Widget / Shortcut Configuration <IMG style="float:right" SRC="icon_tasker.png"/> </H2> This screen allows selection and configuration of a task which will be performed when an icon i... urther on this screen. </P> <P> The layout of the Configuration screen is nearly identical to that of the <A HREF
- app_widgets @tasker:docs:en
- Tapping on the <B>icon</B> of the widget shows a configuration screen where the timer can be configured. </P> <P... <LI>Use the <A HREF="activity_widget_configure">Configuration Screen</A> to configure what should happen when ... L> So a shortcut should be used unless the extra configuration possibilities of a widget are necessary. <H4>Gen
- ah_import_data @tasker:docs:en:help
- ta</H3><P>Dynamically load a task into the active configuration or replace the whole active configuration.<br/><br/>Usually the data to be loaded is first read into a variable via the Read File action.<br/><br/>When a new configuration is successfully loaded, the task (and all others)
- faq-appcreation @tasker:docs:en:faqs
- n the package identifier you specified in the App Configuration screen if the task is running in a child app, oth... e to implement the things in your task or project configuration. Instead, the existing Tasker code is used with t
- activity_scenepropertiesedit @tasker:docs:en
- :right" SRC="icon_tasker.png"/> </H2> <P> Allows configuration of the general properties of a scene. The differe... /B> tab determines which properties are shown for configuration. </P> <UL> <LI><A HREF="#ui">UI</A> <LI><A HREF
- activity_runlog @tasker:docs:en
- e.g. to view the corresponding item from the user configuration. </P> <H3>Details Column</H3> <P> Displays the ... data must be loaded due to the user changing the configuration. </UL> <H5>Profiles</H5> <UL> <LI><I>Active</I>
- activity_locselect @tasker:docs:en
- SRC="icon_tasker.png"/> </H2> This screen allows configuration of a <A HREF="loccontext">Location Context</A>.
- scenes @tasker:docs:en
- e immediately displayed when required without any configuration </UL> <H3>Scene Elements</H3> Each scene is com
- activity_actionedit @tasker:docs:en
- SRC="icon_tasker.png"/> </H2> This screen allows configuration of a single action in a Task. <H4>General</H4>
- activity_elementedit @tasker:docs:en
- :right" SRC="icon_tasker.png"/> </H2> <P> Allows configuration of the properties of a scene element. The differe
- java @tasker:docs:en
- EF="appcreation">App Creation</A>). In the child configuration screen you can add any permissions which your Jav
- sh_plugin @tasker:docs:en:help
- e.<br/><br/>WARNING: data you enter in the plugin configuration screen is collected by the *plugin*, not by Taske
- sh_index @tasker:docs:en:help
- e.<br/><br/>WARNING: data you enter in the plugin configuration screen is collected by the *plugin*, not by Taske