ExeRun (Function)

ONLINE HELP
WINDEV, WEBDEV AND WINDEV MOBILE

Version:

Home | Sign in | English

This content has been translated automatically. Click here to view the French version.

Using a command line
Using the exeActive constant
Return value of a WINDEV executable
Various
Equivalence
Differences between GO mode and runtime
Application in the background: Android 10 specific case

WINDEV

WEBDEV

WINDEV Mobile

Others

See also

ExeRun (Function)

In french: LanceAppli

Starts the execution of a program (an executable for example) from the current application.

This allows you to retrieve:

the return value of executable with the exeReturnValue constant.
the process identifier, also called PID with the exePID constant.

Versions 22 and later

This function is now available for Android applications.

This function is now available in Android Widget mode.

New in version 22

This function is now available for Android applications.

This function is now available in Android Widget mode.

This function is now available for Android applications.

This function is now available in Android Widget mode.

Example

Versions 22 and later

// Start Google Maps
ExeRun("com.google.android.apps.maps")

New in version 22

// Start Google Maps
ExeRun("com.google.android.apps.maps")

Syntax

Running an executable (in locking or non-locking mode) Hide the details

<Result> = ExeRun(<Program name> [, <Mode> [, <Wait for end> [, <Working directory>]]])

<Result>: Boolean

True if the program was started,
False otherwise. ErrorInfo returns more details about the error.

<Program name>: Character string

Name of program to start with its path and/or the parameters that must be passed to the program (if necessary).
If no path is specified, the program is sought in the current directory, then in the Windows directory and in the directories accessible by PATH.
If the executable corresponds to a long name with space characters, the following syntax must be used:
<Program name> = " " " Long_name_with_spaces" " Command_line"
Versions 22 and later
Full name of the application to start (with the package name).
Example: to start the Google Maps application, <Program name> corresponds to: "com.google.android.apps.maps"
New in version 22
Full name of the application to start (with the package name).
Example: to start the Google Maps application, <Program name> corresponds to: "com.google.android.apps.maps"
Full name of the application to start (with the package name).
Example: to start the Google Maps application, <Program name> corresponds to: "com.google.android.apps.maps"

<Mode>: Optional integer constant

Program launch mode (no action on DOS programs).
exeActive
(Default value) The program run is active, it "takes control" over the current program.
exeIconize The program run is inactive and it is minimized.
This constant is not available.
exeInactive The program run is inactive: it is run while the current program keeps focus.
This constant is not available.
exeMaximize The program run is active, it "takes control" over the current program (the execution window is maximized).
This constant is not available.
The program run is always active: it is run by "taking control" over the current program.

<Wait for end>: Optional Boolean constant

Configures the time-out before resuming the execution of the current program:
exeWait The current program resumes its execution when the program run is over.
The application can be started in non-locking mode only. A fatal error occurs if the exeWait constant is used.
exeDontWait
(Default value) The current program and the program run are run in parallel.

<Working directory>: Optional character string

Working directory of application to start.
This parameter is not available.

Starting a program and retrieving a value Hide the details

<Result> = ExeRun(<Program name> [, <Mode> [, <Element to return> [, <Working directory>]]])

<Result>: entier

Sought value:
Return value of the executable if <Element to return> corresponds to the exeReturnValue constant.
PID of the executable if <Element to return> corresponds to the exePID constant.
ErrorInfo is used to find out whether an error occurred.

<Program name>: Character string

Name of program to start with its path and/or the parameters that must be passed to the program (if necessary).
If no path is specified, the program is sought in the current directory, then in the Windows directory and in the directories accessible by PATH.
If the executable corresponds to a long name with space characters, the following syntax must be used:
<Program name> = " " " Long_name_with_spaces" " Command_line"

<Mode>: Optional integer constant

Program launch mode (no action on DOS programs).
exeActive
(Default value) The program run is active, it "takes control" over the current program
exeIconize The program run is inactive and it is minimized
This constant is not available.
exeInactive The program run is inactive: it is run while the current program keeps focus
exeMaximize The program run is active, it "takes control" over the current program (the execution window is maximized)

<Element to return>: Optional constant

Configures the function result:
exeReturnValue The current program resumes its execution when the program run is over. <Result> corresponds to the return value of executable.
exePID The current program and the program run are run in parallel. <Result> corresponds to the identifier of created process (also called PID) if the executable was successfully run, 0 if an error occurred.
This identifier can be used in some APIs for example.

<Working directory>: Optional character string

Working directory of application to start.

Remarks

Using a command line

To pass parameters in command line to the executable run, you must specify the name and full path of the executable to run.

If the program run was developed with WINDEV, OrderLine allows you to retrieve the command line.

Using the exeActive constant

If the process where the application is run (with the exeActive constant) runs a code allowing the calling program to regain focus, the called program loses control.

In order for the called program to keep focus, you must not:

call another window or dialog box after the call to ExeRun,
call ReturnToCapture after ExeRun.

In addition, the Button control (if there is one) whose associated "Click" event contains a call to ExeRun must not be "Tab Stop" ("Accessible by TAB" in the "UI" tab of the control description).

Return value of a WINDEV executable

A WINDEV executable can return a value. All you have to do is:

Create an Integer variable global to the project.
Initialize this variable with the value to return.
Return this variable with the keyword RESULT in the project closing code.

Various

ExeRun does not modify the current directory. The current directory before running ExeRun is identical to the current directory after running ExeRun.
If the program run ignores the specified runtime mode, the program is run in exeActive mode.

Equivalence

ExeRun and ceRunExe have equivalent operating modes.

The only difference is:

ceRunExe runs a program on the Pocket PC from a WINDEV application.
ExeRun runs a program on the Pocket PC from a WINDEV Mobile application.

Differences between GO mode and runtime

In GO mode (simulation on the development computer), the application to start must be found on the development computer.

At run time, the application to start must be found on the Pocket PC.

The differences between GO mode (simulator) and runtime are presented in Differences between GO mode and runtime.

Versions 25 and later

Application in the background: Android 10 specific case

From Android 10, it is no longer possible to open a window when the application is in the background.

ExeRun can open a window. If this function is used while the application is in the background, a fatal error will occur.

Tips:

It is possible to determine if the application is in the background using InBackgroundMode.
If an application needs to interact with the user while it is in the background, the solution is to display a notification (via the Notification type). When the notification is clicked on, the application will be brought back to the foreground if ..ActivateApplication is set to True. It is also possible to open a window from the procedure passed to ..ActionClick.

See Android 10: Behavior of applications in the background for more details.

New in version 25

Application in the background: Android 10 specific case

From Android 10, it is no longer possible to open a window when the application is in the background.

ExeRun can open a window. If this function is used while the application is in the background, a fatal error will occur.

Tips:

It is possible to determine if the application is in the background using InBackgroundMode.
If an application needs to interact with the user while it is in the background, the solution is to display a notification (via the Notification type). When the notification is clicked on, the application will be brought back to the foreground if ..ActivateApplication is set to True. It is also possible to open a window from the procedure passed to ..ActionClick.

See Android 10: Behavior of applications in the background for more details.

Application in the background: Android 10 specific case

From Android 10, it is no longer possible to open a window when the application is in the background.

ExeRun can open a window. If this function is used while the application is in the background, a fatal error will occur.

Tips:

It is possible to determine if the application is in the background using InBackgroundMode.
If an application needs to interact with the user while it is in the background, the solution is to display a notification (via the Notification type). When the notification is clicked on, the application will be brought back to the foreground if ..ActivateApplication is set to True. It is also possible to open a window from the procedure passed to ..ActionClick.

See Android 10: Behavior of applications in the background for more details.

Component : wd260std.dll