The Start Application action can be used to start an application on your computer. Click on the action to add it to your buttons action flow.
The first control is the file chooser. You can click on the three little dots to open the file chooser. You can select an application you want to start by this action.
For some applications you can also pass arguments to have the application start differently. You can use the second field to set your arguments. For example; you can pass the argument -m to Touch Portal to start it minimized. If you are not familiar with this, just leave this empty.
Launching Steam games is not possible in this way. To launch a Steam game you need to use the steam id and use the Open URL action from the category Navigation like this:
Launching Epic games is not possible in the normal way just like Steam games.
To launch an Epic game you need to do similar steps as with the steam-way. First you need
to open the properties of the normal shortcut on your desktop to that game.
It will hold an url that you need to copy and use on an Open URL action
from the category.
Windows apps are a special type of application. They are different from normal executables. Touch Portal has no trouble opening such applications but finding them can be difficult. Here is how you run windows Apps with Touch Portal:
Some applications will not start up using this action. To be able to start such an application, use the Run a shortcut action and point it to a working windows shortcut.
Instead of launching an application directly, Touch Portal also supports to launch a shortcut instead. In the example we pointed to the shortcut of Spotify.
With this action you can open an arbitrary file. Your OS will decide what to do with this. It will choose the application to open the application. Usually this is the application you have associated with the given file type. Sometimes a file has no association. In that case the OS can decided to do nothing. Just point the action to the file you want to open like this:
When this action is executed it will open the specified PDF in this example.
This action allows you to open a folder on your computer. When executed it will open the finder on Mac or the file explorer on Windows at the given folder path. When you open the action it will show a popup where you can choose a path to a folder.
In this example the action will open the C drive on windows using the file explorer.
In Touch Portal you can also run batch files. When you add the action the first control lets you choose three options;
Run script This option will run the script and continue right away. Touch Portal will not wait for the script to finish and it will run the script in the background. Output of the script is also put in the log files of Touch Portal.
Run & wait script This option will run the script and wait for it to finish and it will run the script in the background. Output of the script is also put in the log files of Touch Portal. If the script does not finish, Touch Portal will not continue with the rest of the action flow.
Run & Open This will start the script in a command prompt window, just as it would when you run it from windows. Output will be show in that box just as normal. Touch Portal will not wait and will continue executing the rest of the actions in the flow.
Currently the run batch action will allow 1 argument.
With Touch Portal you can start Powershell scripts directly. When you add the action you have to specify the path of the ps1 script file. You can also add arguments in the second field.
Please note that the path and arguments will be presented to the OS as one command line. This means that you need to use qoutes wherever necessary to have the powershell script parse the correct arguments.
Please note Touch Portal tells the OS that the origin of the script is the working directory of the file. If your script uses relative paths, you need to take account for this. If parts of the script are not working, ensure you use full paths to files and such.
Touch Portal needs to be allowed to execute Powershell scripts. Depending on your windows setup this can be turned off. Follow these steps to get it working:
In Touch Portal actions are executed and when the action is done it will continue to the next action. This action will start the script and then for Touch Portal the action is finished. Touch Portal will not wait for the PowerShell script to stop or anything. If you need to wait before continuing, use the Wait for Timer action to build in some waiting time.
From version 2.3 Touch Portal will log the output of PowerShell scripts for easy debugging and error handling.