WINDEV and WINDEV Mobile manage the following events by default (order of appearance in the code editor):
| |
| Event | Runtime condition |
|---|
| Initializing | Run when opening the window.*
Special case: browsing Looper control filled automatically:
When this code is run, the Looper control is not filled yet. To force the Looper control to be filled in this code, use:
You also have the ability to filter the records with HFilter. |
| End of initialization | Event only for browsing Looper controls filled automatically:
Run once the Looper control has been filled. This code can be used to add or modify an element of the Looper control. |
| Entry in the Looper control | Run when one of the Looper controls takes focus. |
| Exit from the Looper control | Run when moving from one control to another (TAB key, selecting another control with the mouse, etc.). |
| Whenever a Looper control is modified | Run when the user modifies the content of the Looper control. |
| Entry in edit in a row of the Looper control | Run when the user selects a row to enter data. |
| Exit from a row of the Looper control | Run when moving from one row or control to another (TAB key, selecting another control with the mouse, etc.). |
| Displaying a row of the Looper control | Run when a new row must be displayed in the Looper control: redisplaying the Looper control, etc. |
| Selecting a row of the Looper control | Run when the user selects a row (without input). |
 Versions 20 and later New in version 20 | This event is automatically added when the "Pull to refresh" feature is enabled ("Details" tab in the description window of Looper control).
This event is run when a refresh gesture is detected on the Looper control. Once this event has been run, the refresh bar will be automatically hidden except if LooperRefreshVisible is called. |
Versions 18 and later New in version 18 | Event only available if an automatic deletion on row swipe has been defined ("Details" tab of the control description) Run before the automatic deletion of record displayed in the row. This event is used to run different tests for example. If this event returns False the deletion is not performed. |
Versions 18 and later New in version 18 | Event only available if an automatic deletion on row swipe has been defined ("Details" tab of the control description) Run after the effective deletion of the record. This event is used, for example, to re-display the data. |
Versions 18 and later New in version 18 | Event only available if an action on row swipe has been defined ("Details" tab of the control description)- Case of automatic deletion: This event is executed BEFORE the event "Before deleting a row". If this event returns False, the event "Before automatically deleting a row" is not run and the record is not deleted.
- Case of action by programming: This event is run when the user swipes the row. This event allows you to program the desired action.
|
Versions 18 and later New in version 18 | Run at the beginning of Drag/Drop for the element. This event is used to run different tests for example. If this event returns False the movement is not performed. |
Versions 18 and later New in version 18 | Run when the user finishes the element Drag/Drop. If this event returns False the movement is not performed. |
| Filtering records | Optional code for browsing Looper controls filled automatically:
Run just before displaying a row. This event filters the records displayed in the Looper control. This event is detailed at the end of this page. |
(*) 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: