event xforms-value-changed in fr:select1-button

Good Morning together,

how would I get the event 'xforms-value-changed' from a
'fr:select1-button' if a user changes the selection?

https://gist.github.com/hgoetzger/1552d867783ddace0c7a shows an example.
This used to work in 3.9 but unfortunately not in 4.[45].

Thanks

Cheers

Heinrich

--
Before printing this e-mail, think about our environmental responsibility.

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

Hi Heinrich,

Before 4.0, xforms-value-changed just "escaped" from the inside of the component. But this doesn't happen anymore with 4.0+, as now events are not allowed to just escape the component's inner scope. (More on this in the section linked below).

http://wiki.orbeon.com/forms/doc/developer-guide/xbl-components-guide#TOC-With-Orbeon-Forms-44

So the component would need to be modernized to use xxbl:mode="lhha binding value", like the databound-select1.

https://github.com/orbeon/orbeon-forms/blob/master/src/resources-packaged/xbl/orbeon/databound-select1/databound-select1.xbl

Other than that, is the component working for you? (I am asking since we haven't touched it in a while.)

Alex

Hoi Alex,

thanks for the quick response.

Well, the component works. We can choose an option and we see the change
in the instance, take a look at the gist mentioned in the OP. And it
looks good in different clients.

So we worked until now on an accidentally escaping update-event of the
component. Wow :-)
But the event xforms-ready "escapes" on purpose, if I understand the
xbl-code correctly.

To get the action of the user changing a selection would need to be
handled in a different way now. Until now we reference the selection in
a bigger 'global' instance which will be used in a dispatched event on
the xforms-value-changed event. I'd need to establish an
interims-instance where I set up an action to listen on the
xxforms-value-changed and set and use then the 'old' and existing code then.

Using the event xforms-select catches every handling of the selector,
even if the user is not changing a selection.

And, yes, there might be some more efficient ways, but you know, time
and space .....

Cheers!

Heinrich

On 05/10/14 02:41, Alessandro Vernet wrote:

--
Before printing this e-mail, think about our environmental responsibility.

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].