W3C home > Mailing lists > Public > public-xformsusers@w3.org > April 2017

Re: Refresh action

From: Steven Pemberton <steven.pemberton@cwi.nl>
Date: Wed, 12 Apr 2017 11:37:00 +0200
To: "Erik Bruchez" <ebruchez@orbeon.com>
Cc: XForms <public-xformsusers@w3.org>
Message-ID: <op.yykszyhksmjzpq@steven-xps>
I put it in the description of the refresh action, here:

https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_refresh_Element

Steven

On Wed, 12 Apr 2017 11:22:09 +0200, Steven Pemberton  
<steven.pemberton@cwi.nl> wrote:

> Thanks, that's good information.
>
> I'll try to work it into the spec as a note.
>
> Steven
>
> On Tue, 11 Apr 2017 19:53:58 +0200, Erik Bruchez <ebruchez@orbeon.com>  
> wrote:
>
>>> I understand the need for rebuild and recalculate, less the need for  
>>> revalidate, but I can't imagine any use case for refresh.
>>
>> Refresh as a side-effect dispatches UI events (`xforms-value-changed`,  
>> etc.). So if you are running an action and want *everything* in your  
>> form to be up to date in the middle >>of an action, then `refresh`  
>> allows you to do that. Note that other actions, such as `toggle` and  
>> `setindex` in effect force a refresh as part of their execution.
>>
>> In addition, any function which requires asking controls themselves for  
>> information, such as `index()`, `case()`, will be up to date only after  
>> a refresh.
>>
>> I have used `refresh` on occasion.
>>
>> -Erik
Received on Wednesday, 12 April 2017 09:37:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:37:48 UTC