PC SOFT

WINDEVWEBDEV AND WINDEV MOBILE
ONLINE HELP

Home | Sign in | English UK
  • Events managed by default
  • Optional events
  • Move application to the foreground
  • Move the application to the background
  • Changing the layout
  • Specific optional event: Application of light/dark theme
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
Events managed by default
WINDEV and WINDEV Mobile manage the following events by default (order of appearance in the code editor):
EventRuntime condition
Global declarationsDeclaring the variables global to the window. This is the first code run when opening the window.
End of initializationRun when the window is opened.
The events are run in the following order:
  • Initializing the window controls (*)
  • Initializing the window
  • Focus gain
Remark: A blinking effect may appear if the code for updating the controls is included in this event. Indeed, the initialization code of controls is run before the update code.
ClosingRun when closing the window.
Remark: Resuming the input in one of the window controls in this code prevents from closing the window.
Versions 20 and later
Request for refreshing the display
New in version 20
Request for refreshing the display
Request for refreshing the display
Used to group the code for updating the window controls: content of controls, state (visible, grayed, etc.), caption to refresh, etc.
This event can receive parameters. Simply declare a procedure in the event. For example:
// Request for refreshing the display
PROCEDURE AskForRefresh(RefreshType is boolean)
This event is started upon request by the following functions:
When these functions are called, you can specify the value of the parameters expected by the event.
Windows Mobile Before closing with OK/Close button
Run when using the OK/Close button
Operating mode of the Close button
The following events are run:
  • "Before closing with OK/Close button" is run.
  • running the code of the "Cancel" button found in the window (if this button exists). If the window contains no "Cancel" button, the window is closed.
Operating mode of the OK button
The following events are run:
  • "Before closing with OK/Close button" is run.
  • running the code of "Validate" button found in the window (if this button exists). If the window contains no "Validate" button, the window is closed.
Remark: The window will not be closed if the event "Before closing with OK/Close button" calls ReturnToCapture.
AndroidAndroid Widget iPhone/iPadUniversal Windows 10 App This event is not available.
Focus gainRun when the window takes focus (the title bar is active) and when another window loses focus:
  • the user clicked another window of the application
  • ReturnToCapture was run from another window of the application
This event will not be run:
  • when opening the first project window.
  • when running OpenChild, OpenMobileWindow or OpenSister from the current window.
  • if Close is called in the window initialization code.
  • if the user clicks a window of another program then re-clicks the initial window.
AndroidAndroid Widget Universal Windows 10 App This event is not available.
Focus lossRun when the window loses focus when going to another window. This event is always called before the focus gain event of another window in the following cases:
  • closing the window (before the closing event)
  • the user clicked another window of the application
  • ReturnToCapture was run from another window of the application
This event will not be run:
  • if ReturnToCapture to another window was run in the window initialization code
  • if Close is called in the window initialization code
  • if the user clicks a window of another program then re-clicks the initial window
AndroidAndroid Widget Universal Windows 10 App This event is not available.
Whenever modifiedRun when one of the window controls is modified (input performed by the user for example).
Versions 17 and later
AndroidUniversal Windows 10 App Change of orientation
New in version 17
AndroidUniversal Windows 10 App Change of orientation
AndroidUniversal Windows 10 App Change of orientation
Run when the user turns the screen around. This allows you to reposition the controls when changing the orientation of the screen.
AndroidiPhone/iPadUniversal Windows 10 App Closing a child window of the window
Run when closing a child window opened from the current window.
You can:
  • find out the name of the child window that was closed via ..Name.
  • retrieve the return value of child window via ..ReturnedValue.Example:
// -- Close a child window of WIN_OrderList
// Refreshes the list of orders if necessary
IF MyChildWindow..ReturnedValue = True THEN
OrderList()
END
The MyChildWindow keyword is used to handle the characteristics of the child window.
ResizingRun in the following cases:
  • Minimizing the window
  • Enlarging or resizing the window
  • Restoring the window once it was minimized
Universal Windows 10 App This event is not available.
Versions 18 and later
Android Widget Refreshing the Widget
New in version 18
Android Widget Refreshing the Widget
Android Widget Refreshing the Widget
Used to update the Widget content. This event is run:
  • when opening a Widget window.
  • at regular time interval. This interval is defined in the "Details" tab of description window.
Remark: WidgetDisplay redisplays the Widget and runs the refresh event.

(*) By default, the event "Initializing" of each control is run according to the order in which the controls were created in the window. To modify this runtime order:
  1. On the "Window" pane, in the "Order" group, click "Initialization".
  2. In the window that is displayed, use the arrows on the right to modify the initialization order of controls.
Caution: If one or more controls use the persistence of controls, the "Whenever modified" code can be run when initializing the control. See Persistence of controls for more details.
Optional events
Several optional events can be managed. To add an optional event:
  1. Select the requested control.
  2. Display the code window of this control (F2 key).
  3. Click the link "Add other events to xxx" at the bottom of the window code, after the last event.
  4. All the optional events available for the control are displayed.
  5. Check the optional event to add and validate.
    Remark: You can select several optional events.
  6. The selected optional event is automatically added to the events managed by the control.
To disable an optional event, simply perform the same operations to display the list of optional events. Then simply uncheck the optional events to delete.
Remark: If the disabled code contains WLanguage code, this code is automatically deleted.
You can manage, for example:
  • the mouse hover over the control,
  • the left mouse button down, up, with a double click,
  • right mouse button down, up, with double click,
  • the mouse wheel, etc.
Versions 18 and later
AndroidiPhone/iPad

Move application to the foreground

Run when the application is re-enabled and when it is moved to the foreground. This event is used, for example, to refresh the displayed data.
Remark: This event is run AFTER the event "Move to the foreground" of the project.
New in version 18
AndroidiPhone/iPad

Move application to the foreground

Run when the application is re-enabled and when it is moved to the foreground. This event is used, for example, to refresh the displayed data.
Remark: This event is run AFTER the event "Move to the foreground" of the project.
AndroidiPhone/iPad

Move application to the foreground

Run when the application is re-enabled and when it is moved to the foreground. This event is used, for example, to refresh the displayed data.
Remark: This event is run AFTER the event "Move to the foreground" of the project.
Versions 18 and later
AndroidiPhone/iPad

Move the application to the background

Run when the application is moved to the background. This event is used, for example, to save the data.
Remark: This event is executed BEFORE the event "Move to the background" of the project.
New in version 18
AndroidiPhone/iPad

Move the application to the background

Run when the application is moved to the background. This event is used, for example, to save the data.
Remark: This event is executed BEFORE the event "Move to the background" of the project.
AndroidiPhone/iPad

Move the application to the background

Run when the application is moved to the background. This event is used, for example, to save the data.
Remark: This event is executed BEFORE the event "Move to the background" of the project.
Versions 23 and later
WINDEVAndroidiPhone/iPad

Changing the layout

Run when the layout is automatically modified.
Remark: WinChangeLayout does not trigger this event.
New in version 23
WINDEVAndroidiPhone/iPad

Changing the layout

Run when the layout is automatically modified.
Remark: WinChangeLayout does not trigger this event.
WINDEVAndroidiPhone/iPad

Changing the layout

Run when the layout is automatically modified.
Remark: WinChangeLayout does not trigger this event.
Versions 25 and later
AndroidiPhone/iPad

Specific optional event: Application of light/dark theme

If the dark theme is enabled in the project, the optional event "Application of light/dark theme" is available. This event allows you to manage special cases to switch between light and dark theme.
This event is run in the following cases:
  • When the window is opened, after the "Global declarations" event and before the initialization events of the window controls.
  • If the window is open when changing the theme by programming with ChangeTheme, only if the withCodeExecution constant has been specified.
  • If the window is open when the system automatically changes the theme: modification of system settings, changing the day/night time, activating/deactivating the battery saver, etc.
See Dark theme management on mobile for more details.
New in version 25
AndroidiPhone/iPad

Specific optional event: Application of light/dark theme

If the dark theme is enabled in the project, the optional event "Application of light/dark theme" is available. This event allows you to manage special cases to switch between light and dark theme.
This event is run in the following cases:
  • When the window is opened, after the "Global declarations" event and before the initialization events of the window controls.
  • If the window is open when changing the theme by programming with ChangeTheme, only if the withCodeExecution constant has been specified.
  • If the window is open when the system automatically changes the theme: modification of system settings, changing the day/night time, activating/deactivating the battery saver, etc.
See Dark theme management on mobile for more details.
AndroidiPhone/iPad

Specific optional event: Application of light/dark theme

If the dark theme is enabled in the project, the optional event "Application of light/dark theme" is available. This event allows you to manage special cases to switch between light and dark theme.
This event is run in the following cases:
  • When the window is opened, after the "Global declarations" event and before the initialization events of the window controls.
  • If the window is open when changing the theme by programming with ChangeTheme, only if the withCodeExecution constant has been specified.
  • If the window is open when the system automatically changes the theme: modification of system settings, changing the day/night time, activating/deactivating the battery saver, etc.
See Dark theme management on mobile for more details.
Minimum version required
  • Version 9
This page is also available for…
Comments
Click [Add] to post a comment