07-28-2022, 07:12 AM
(07-28-2022, 03:01 AM)Alexandre Machado Wrote: Not exactly performant, yes, in case you have such a big grid. I'll have a look at the IWEdit refresh and why it is not working.
Regarding the EventParams, there is actually no requirement that the field needs to have the same name as the component. The component itself handles this internally in a transparent way. In general you don't need to deal with it directly, do you?
Each TIWControl has a method like this:
function TIWCustomCheckBox.IsForThisControl(AName: string): Boolean;
begin
Result := SameText(HTMLName + '_CHECKBOX', AName);
end;
So, the IWCheckBox itself knows what field name it expects.
Regarding TIWEdit.RefreshAsyncRender:
It is not only TIWEdit but also all other controls; probably TIWCustomControl.RefreshAsyncRender.
Regarding EventParams:
Normally you don't need it. However, if you need to generate controls dynamically in frames in asynchronous events, then you need it.
Example:
Frame1 contains Button1.
An additional control must be generated in Button1.OnAsyncClick, which in turn has an asynchronous event.
In this event, it is only possible to react to a changed value of the control using the EventParams with the name of the control.
Is that correct or do I have a misconception?
Kind regards
The way to success is always under construction ... but i see a light at the end of the tunnel

