|
|
|
|
|
- "Request for refreshing the display" event
- "Presenter" attribute
RequestRefreshUI In french: DemandeMiseAJourUI Requests the execution of the "Request for refreshing the display" event (and gives back control without waiting for the execution of the event). This function is mainly used:
MySelf.Title = gpclContactForm.p_sFullname
SourceToScreen()
Syntax
RequestRefreshUI([<Parameter 1> [... [, <Parameter N>]]])
<Parameter 1>: Optional parameter corresponding to the type expected by the "Request for refreshing the display" event First parameter that will be passed to the "Request for refreshing the display" window event. <Parameter N>: Type of value expected by the "Request for refreshing the display" event Nth parameter that will be passed to the "Request for refreshing the display" window event. Remarks "Request for refreshing the display" event One of the events associated with the window is "Request for refreshing the display". This event is used to group the code for refreshing the window controls: contents of controls, state (visible, grayed out...), text to refresh, etc, ... This event is available on windows, internal windows, pages, internal pages, control templates and supercontrols. This event can receive parameters. Simply declare a procedure in the event. For example:
PROCEDURE AskForRefresh(RefreshType is boolean)
This event is started upon request by the following functions: - RequestRefreshUI: Executes the "Request for refreshing the display" event of the current element at the end of the current process (asynchronous execution).
- ExecuteRefreshUI: Immediately executes the "Request for refreshing the display" event of the current element.
- RequestRefreshUIElement: Executes the "Request for refreshing the display" event of the given element at the end of the current process (asynchronous execution).
- ExecuteRefreshUIElement: Immediately executes the "Request for refreshing the display" event of the given element.
- RequestRefreshUIParent: Executes the "Request for refreshing the display" event of the higher level at the end of the current process (asynchronous execution).
- ExecuteRefreshUIParent: Immediately executes the "Request for refreshing the display" event of the higher level.
When these functions are called, you can specify the value of the parameters expected by "Request for refreshing the display". Remarks: - The code that calls RequestRefreshUI determines the element whose event "Request for display update" is executed. If it is a class with the presenter attribute, the element will be the window associated with the class. Otherwise, it will be the element from which the code was executed.
- If RequestRefreshUI is called multiple times, all subsequent calls with the same parameters as calls that have not yet been executed are ignored.
- If RequestRefreshUI is called in main the thread, the "Request for refreshing the display" event will be executed after the current process.
- If RequestRefreshUI is called in a secondary thread, the "Request for refreshing the display" event will be executed when the window is refreshed.
Related Examples:
|
Cross-platform examples (WINDEV Mobile): WM Discover MVP
[ + ] This example shows the implementation of an MVP (Model View Presenter) architecture in a project. This example has been simplified to better explain the concepts of this architecture.
|
|
Training (WINDEV): WD Discovering MVP - Part 1
[ + ] This educational example explains how to implement an MVP architecture (Model View Presenter) in a project. This example is simplified in order easily understand the concepts of this architecture.
|
|
Training (WINDEV): WD Discovering MVP - Part 2
[ + ] This training example explains how to implement an MVP architecture (Model View Presenter) in a project for a simple analysis (Customer - Order - Order line - Product). Several types of views (as well as their presentation) are proposed: - table (with addition, modification, deletion and print), - form, - search (with filter).
|
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|