PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Processes managed by default
  • Processes managed by WINDEV and WINDEV Mobile
  • Processes managed by WEBDEV
  • Filtering the records (browsing looper only)
  • Click performed on a looper (browser code only)
  • Optional processes
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
Processes associated with the Looper controls
Processes managed by default
WINDEVAndroidiPhone/iPadWindows MobileUniversal Windows 10 AppJava

Processes managed by WINDEV and WINDEV Mobile

WINDEV and WINDEV Mobile manage the following processes by default (in the order in which they appear in the code editor):
ProcessRuntime condition
InitializingRun when opening the window.*

Special case: Browsing looper automatically filled:
When this code is run, the looper is not filled yet. To force the looper to be filled in this code, use:
You also have the ability to filter the records with HFilter.
End of initializationProcess found for the browsing Looper controls automatically filled:
Run once the looper was filled. This code can be used to add or modify a looper element.
Entry in the looperRun when one of the looper controls takes focus.
Exit from the looperRun when changing control (TAB key, change of control with the mouse, ...)
Whenever the looper is modifiedRun when the user modifies the looper content.
Universal Windows 10 App This process is not run.
Enter in input in a looper rowRun when the user selects a row to perform an input in this row.
Universal Windows 10 App This process is not run.
Exit from a looper rowRun when changing row or when changing control (TAB key, change of control with the mouse, ...) from a row.
Universal Windows 10 App This process is not run.
Displaying a looper rowRun when a new row must be displayed in the looper: re-display of the looper, ...
Universal Windows 10 App This process is not run.
iPhone/iPad This process is not available in the browsing Looper controls for performance reasons.
Selecting a looper rowRun when the user selects a row (without input).
Versions 20 and later
AndroidiPhone/iPad Pull to refresh
New in version 20
AndroidiPhone/iPad Pull to refresh
AndroidiPhone/iPad Pull to refresh
This process is automatically added when the "Pull to refresh" feature was enabled ("Details" tab in the description window of Looper control).
This process is run when a refresh gesture is detected on the Looper control.
At the end of this process, the refresh bar will be automatically hidden except if LooperRefreshVisible was called.
Versions 18 and later
AndroidiPhone/iPad Before automatically deleting a row by swipe
New in version 18
AndroidiPhone/iPad Before automatically deleting a row by swipe
AndroidiPhone/iPad Before automatically deleting a row by swipe
Process found only if an automatic deletion was defined when swiping a row ("Details" tab of control description)
Run before the automatic deletion of record displayed in the row. This process is used to run different tests for example. If this process returns False, the deletion is not performed.
Versions 18 and later
AndroidiPhone/iPad After automatic deletion of a row by swipe
New in version 18
AndroidiPhone/iPad After automatic deletion of a row by swipe
AndroidiPhone/iPad After automatic deletion of a row by swipe
Process found only if an automatic deletion was defined when swiping a row ("Details" tab of control description)
Run after the effective deletion of the record. This process is used to redisplay the data for example.
Versions 18 and later
Android Swipe of a row
New in version 18
Android Swipe of a row
Android Swipe of a row
Process found only if an action was defined when swiping a row ("Details" tab of control description)
  • Case of automatic deletion: This process is run BEFORE the "Before deleting a row" process. If this process returns False, the "Before automatically deleting a row" process is not run and the record is not deleted.
  • Case of action by programming: This process is run when the row is swiped by the user. This process is used to program the requested action.
Versions 18 and later
Android Beginning of source Drag/Drop
New in version 18
Android Beginning of source Drag/Drop
Android Beginning of source Drag/Drop
Run at the beginning of Drag/Drop for the element. This process is used to run different tests for example. If this process returns False, the move is not performed.
Versions 18 and later
Android Drop in target Drag/Drop
New in version 18
Android Drop in target Drag/Drop
Android Drop in target Drag/Drop
Run at the end of Drag/Drop for the element. If this process returns False, the move is not performed.
Filtering the recordsOptional code found for the browsing Looper controls filled automatically:
Run just before displaying a row. This process is used to filter the records that must be displayed in the looper control. This process is presented in details at the end of this page.
Android This process is not available.

(*) By default, the "Initializing" process of each control is run according to the creation order of controls in the window. To modify this runtime order:
  1. Select "Windows .. Edit the initialization order".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.
WEBDEV - Server codeWEBDEV - Browser codePHP

Processes managed by WEBDEV

WEBDEV manages the following processes by default (in the order in which they appear in the code editor):
ProcessRuntime condition
Initialization (Server code)Run when opening the page.
Special case: Browsing looper automatically filled:
When this code is run, the looper is not filled yet. To force the looper to be filled in this code, use:
End of initialization (Server code)Code found for a browsing Looper automatically filled:
Run once the looper was filled. This code can be used to add or modify a looper element.
Row display (Server code)Run when a new row must be displayed in the looper: re-display of the looper, ...
Used to manage the calculated attributes.
Filtering records (Server code)Code found for the browsing looper automatically filled:
Run just before displaying a row. This process is used to filter the records that must be displayed in the looper control. This process is presented at the end of this page.

Note: Only the optional processes are available in a static page.
Filtering the records (browsing looper only)
WINDEVWEBDEV - Server codeiPhone/iPadWindows MobileUniversal Windows 10 AppPHP The "Filtering the records" process is run just after the display of a looper row. Therefore, it is run:
  • when initializing the looper.
  • whenever a new looper row is displayed.
This process is used to filter the records displayed in the Looper control.
To implement a filter, the "Filtering records" process must return a value:
  • True to specify that the record matches to the filter and that it must be displayed.
  • False to specify that the record does not match the filter and that it must not be displayed.
  • Cancel to stop reading the data source of the looper (very rare case).
Example:
// -- Filter the records
// Displays the customers who placed orders exceeding 3000 Euros
IF Order.TotalIOT >= 3000 THEN
RESULT True
ELSE
RESULT False
END
In this code, the data handled affects the record currently read by the looper. This data comes from the data file or from the query linked to the looper.
Note: In WINDEV and WINDEV Mobile, the "Filtering the records" process is an optional process. In WEBDEV, this process is proposed by default.
Click performed on a looper (browser code only)
WEBDEV - Browser code The "Click on looper" process is run when the user clicks a looper row.
Versions 17 and later
This process is used to select the row. This process returns the values of the attributes corresponding to the row. For example, the following click code is used to find out the value of the ATT_Title attribute for the row that was clicked:
Trace(ATT_Title)
New in version 17
This process is used to select the row. This process returns the values of the attributes corresponding to the row. For example, the following click code is used to find out the value of the ATT_Title attribute for the row that was clicked:
Trace(ATT_Title)
This process is used to select the row. This process returns the values of the attributes corresponding to the row. For example, the following click code is used to find out the value of the ATT_Title attribute for the row that was clicked:
Trace(ATT_Title)
Optional processes
Several optional processes can be managed.
To manage an optional process, all you have to do is select it in the icon bar of code window.
WINDEV and WINDEV Mobile
WEBDEV
To add an optional process:
  1. Select the requested control.
  2. Display the code window of this control ([F2] key).
  3. Click the link "Add other processes to xxx" found at the end of window code, after the last process.
  4. All the optional processes available for the control are displayed.
  5. Check the optional process to add and validate.
    Note: You have the ability to select several optional processes.
  6. The selected optional process is automatically added into the processes managed by the control
To disable an optional process, perform the same operations to display the list of optional processes. Then, all you have to do is uncheck the optional processes to delete.
Note: If the disabled code contains WLanguage code, this code is automatically deleted.
You have the ability to manage:
  • the left mouse button down, up, with a double click,
  • the right mouse button down, up, ...
See the Optional processes for more details.
Minimum required version
  • Version 9
This page is also available for…
Comments
Click [Add] to post a comment