>
>
> Alessandro  Vernet wrote:
>>
>> I see. Another option, with the current code, is to "set a flag"
>> (store in an element <submission-in-progress> of an  instance "true"
>> instead of "false") before you do the <xforms:send>. Then on
>> xforms-submit-done you reset the flag, and in xforms-value-changed,
>> you don't do anything if the flag is set.
>>
>
> I've tried to solve my problem like this, but my attempts failed, because
> xforms-submit-done is sent before the RRRR (refresh - which causes undesired
> xforms-value-changed, rebuild, recalculate, revalidate), so the resetting
> happend too early. Is there any event that marks "the end of submission and
> of all of its consequences" (RRRR)? I attach an excerpt from my event log
> here: http://gamma.mini.pw.edu.pl/~arciuchm/log.txt
>
> This would be perfect place to place a trigger resetting another flag, the
> "dirty" flag (a flag that informs that the document has been modified after
> last save).
>
> Anyways, huge thanks for providing me with the development build, Maciek
> --
> View this message in context: http://n4.nabble.com/A-problem-with-unnecessary-xforms-value-changed-after-replace-instance-submission-and-one-more-thing-tp252592p253279.html
> Sent from the ObjectWeb OPS - Users mailing list archive at Nabble.com.
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>
>