Help / WLanguage / WLanguage functions / Standard functions / Windows management functions / Application update functions
  • Overview
  • Characteristics of window
  • Programming
  • Procedure associated with the custom window
  • Calling the custom window
  • Stopping the application
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WindowsLinuxPHPWEBDEV - Browser code
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac CatalystUniversal Windows 10 App
Stored procedures
To customize the remote control performed on a multi-user WINDEV application, the standard window can be replaced with a window from your application.
This window will be used:
  • to display the message indicating that the connection cannot be established,
  • to display the warning message,
  • to display the message for closing the application.
This window must respect some norms, both for display and programming.
Characteristics of window
The custom window must contain the following elements:
  • a control used to display the message to the users,
  • a procedure used to retrieve the parameters passed to the window (see the programming paragraph).
This window can contain any control, process, etc. custom.

Procedure associated with the custom window

A procedure must be declared in the global declaration of global variables of the window. Indeed, when this window is opened by the mechanism for remote control, the parameters passed to this window can be retrieved by programming.
This window must be associated with a procedure of the following type:
PROCEDURE <Window Name>(<Mode>, <Message>, <Display Duration>)
where the parameters are as follows:
<Mode>Retrieves as constants the current mode for remote control:
  • acForbidden: access denied to the application
  • acWarning: warning of imminent shutdown
  • acStop: application shutdown
<Message>Retrieves the message corresponding to the current mode (this message must be displayed in the window)
<Display duration>Maximum display duration of the window (in seconds)
// Declaration code of the global variables of WIN_CustomMessage
PROCEDURE WIN_CustomMess(AccessMode, MessageToDisplay, DispDuration)
SWITCH AccessMode
CASE acForbidden: IMG_IconControl.Image = "Forbidden.BMP"
CASE acWarning: IMG_IconControl.Image = "Info.BMP"
CASE acStop: IMG_IconControl.Image = "Stop.BMP"
EDT_MessageControl = MessageToDisplay

Calling the custom window

To use the custom window to automatically check your application, AppControl must be called in the initialization code of your project:
AppliControl("U:\MyApp\WDUPDATE.NET", WIN_CustomMessage)
  • WIN_CustomMess is the name of the custom window,
  • "WDUPDATE.NET" is the control file of the application.
Tip: The call to AppControl must be the first statement found in the initialization code of project.

Stopping the application

When using a custom window, the stop mode defined for the application (acStop constant) does not automatically stop the application. The call to EndProgram must be included in your application.
Minimum version required
  • Version 9
Click [Add] to post a comment

Last update: 05/26/2022

Send a report | Local help