| Dave,
The xml specification allows for <control-state> on these widgets. Note that the order of the elements is important, so for <button-group> (for example), the order must be <layout-data>, <layout>, <title>, <tooltip>, <button>, and only then <control-state>.
Looking into the other issue…
Greg On Apr 23, 2012, at 4:53 PM, Dave Wootton wrote: I'm trying to use the hide-if and show-if
capability to dynamically hide and show widgets in a JAXB resource manager
definition and have run into a couple limitations. For example I added
this XML snipped to a widget specification
<control-state>
<hide-if
button="use_ll" selected="true"/>
</control-state>
1) This is only accepted for <widget>
specifications. If I try to add it to a button-group, radiobutton, browse
or other compound widget type I get an error that the XML file is invalid.
2) I'm trying to control the visibility
of widgets in the scope of multiple <dynamic> specifications (multiple
tabs) by checking the state of a widget (radio button) on one of the tabs.
The problem is that the buttonId specification is valid only within the
scope of the <dynamic> specification where it appears.
I can work around this by coding the
same button specification (for a "use LoadLeveler" radio button
pair) in each <dynamic> specification so the same button pair appears
in each tab, and references the same attribute specification so the button
pair in each tab is always the same state but this seems redundant.
I could also solve this if there was
a way to code a radio button pair outside the scope of a dynamic tab where
widgets in each tab can find it by buttonId but I don't see a way to do
that.
Dave_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
|
