Marcus,
> i just updated to the yesterday nightlybuild of OPS and now some of my
> readonly binding don't work anymore!
> To have an reproducable example just look at the Govermanet-Forms! There
> they don't work at all!
>
> When opening the first time and with no documents found, all controls
> except "add new" should be disabled and readonly, but that does not
> work! Any hint on this? I need that to get work again :-(
It turns out that this is a new "feature" that we introduced last week
(in fact, a bug fix).
What happened before was that if you wrote this:
<xforms:group ref="some-node">
<xforms:trigger>
...
Then the trigger would inherit the read-only property of the enclosing
group. But this is not right, because the trigger is not bound to any
node so must not inherit MIPs this way.
So you can fix it this way:
<xforms:group ref="some-node">
<xforms:trigger ref=".">
...
or:
<xforms:group>
<xforms:trigger ref="some-node">
...
depending on the situation.
I have made the changes in the Government Forms and the To-Do Lists
example as well.
Note that relevance is different, because the XForms spec says that
all the descendants of a non-relevant group become non-relevant as
well. But this does not apply to read-only-ness unless you bind the
trigger.
-Erik
--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.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
ObjectWeb mailing lists service home page:
http://www.objectweb.org/wws
Locked
