AYUDA EN LÍNEA
 WINDEV, WEBDEV Y WINDEV MOBILE
Este contenido se ha traducido automáticamente.  Haga clic aquí  para ver la versión en inglés.
Ayuda / Desarrollar una aplicación o un sitio web / Controles, ventanas y páginas / Controles: tipos disponibles / Control Looper
  • Default events
  • Events supported in WEBDEV
  • Filter records (Looper based on a data file only)
  • Click on a Looper control (browser code only)
  • Optional events
WINDEV
WindowsLinuxJavaReportes y ConsultasCódigo de Usuario (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Código Navegador
WINDEV Mobile
AndroidWidget Android iPhone/iPadIOS WidgetApple WatchMac Catalyst
Otros
Procedimientos almacenados
Events associated with Looper controls
Default events
WEBDEV - Código ServidorPHP

Events supported in WEBDEV

The following events appear by default in the WEBDEV code editor:
EventRuntime condition
Initialization (Server code)Executed when the page is opened.
Special case: RepeatString zone automatically fills file:
When this code is run, the Looper control is not filled yet. To force the Looper control to be filled in this code, use:
End of initialization (Server code)Code only for Looper controls populated automatically based on a data file:
Run once the Looper control has been filled. This code can be used to add or modify an element of the Looper control.
Row display (Server code)Executed when a new row is to be displayed in the RepeatString field: redisplay of the RepeatString field, ...
Used to manage calculated attributes.
Filter records (Server code)Code only for Looper controls populated automatically based on a data file:
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.

Note: In a static page, only optional events are available.
Filter records (Looper based on a data file only)
WEBDEV - Código ServidorPHP The event "Filtering the records" is run right after a row of the Looper control is displayed. Therefore, it is run:
  • when initializing the Looper control.
  • whenever a row is displayed in the Looper control.
This event filters the records displayed in the Looper control.
To implement a filter, the "Filter records" event 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 control (very rare case).
Example: 
// -- Filtrage des enregistrements --
// Affiche uniquement les clients dont commandes sont supérieures à 3000 euros
IF Commande.TotalTTC >= 3000 THEN 
	RETURN True
ELSE
	RETURN False
END
In this code, the data handled affects the record currently read by the Looper control. This data comes from the data file or query linked to the Looper control.
Note: In WINDEV and WINDEV Mobile, the "Record filtering" event is optional.. In WEBDEV, this event is proposed by default.
Click on a Looper control (browser code only)
The "Click on the Looper control" event is executed when the user clicks on a row of the Looper control. This process is used to select the row. This event 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_Titre)
Optional events
Several optional events can be added. To add an optional event:
  1. Select the desired 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.
    Note: Several optional events can be selected.
  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.
Note: If the deactivated code contains WLanguage code, this code is automatically deleted..
For example, you can use the following events:
  • left mouse button down, up, double click,
  • right button down, up, etc.
For more details, see the Optional events.
Ver también
Versión mínima requerida
  • Versión 9
Esta página también está disponible para…
Comentarios
Haga clic en [Agregar] para publicar un comentario

Última modificación: 18/09/2024

Señalar un error o enviar una sugerencia | Ayuda local