one more ConfigUI level

Posted on
Mon Mar 10, 2014 3:02 pm
kw123 offline
User avatar
Posts: 8392
Joined: May 12, 2013
Location: Dallas, TX

one more ConfigUI level

can I add configUI in a configUI?

like here - indicated with "<==== this one"
Code: Select all
   
   <Device type="custom" id="sceneExample">
      <Name>Scene</Name>
      <ConfigUI>
         <Field id="sourceDeviceMenu" type="menu">
            <Label>Device to add to scene:</Label>
            <List class="self" method="sourceDevices" dynamicReload="true"/>
         </Field>
         <ConfigUI>       <==== this one
             <Field id="addDevice" type="button">
                <Label/>
               <Title>Add Device</Title>
              <CallbackMethod>addDevice</CallbackMethod>
              </Field>
         </ConfigUI>   <==== this one end
         
         <Field id="memberDeviceList" type="list">
            <Label>Devices in scene:</Label>
            <List class="self" method="memberDevices" dynamicReload="true"/>
         </Field>
      </ConfigUI>
   </Device>
</Devices>




Karl
this one does not work..

Posted on
Mon Mar 10, 2014 3:29 pm
matt (support) offline
Site Admin
User avatar
Posts: 21429
Joined: Jan 27, 2003
Location: Texas

Re: one more ConfigUI level

Nope, only one per device definition.

Image

Posted on
Mon Mar 10, 2014 3:48 pm
kw123 offline
User avatar
Posts: 8392
Joined: May 12, 2013
Location: Dallas, TX

Re: one more ConfigUI level

I recall seeing something like that in one of the plugins that there was a sub menu somewhere but I can't find it..

anyway thanks ...


Karl

Posted on
Wed Mar 12, 2014 8:45 am
matt (support) offline
Site Admin
User avatar
Posts: 21429
Joined: Jan 27, 2003
Location: Texas

Re: one more ConfigUI level

You can bind the visibility of controls to the value of a popup menu. So when item 1 is selected in the popup some other fields are visible, when item 2 is selected other fields are visible, etc. Like what you are doing now, but instead of binding to checkboxes you can bind to a popup (and its value). You could also have Next and Previous buttons which have plugin defined callback actions that increment/decrement the selected value in a popup. If you go the Next/Previous button route, then you could also make the popup invisible if you wanted to (so its purpose would only be to server as a visibility binding target for the controls, not an end user visible UI control).

Image

Posted on
Wed Mar 12, 2014 10:48 am
kw123 offline
User avatar
Posts: 8392
Joined: May 12, 2013
Location: Dallas, TX

Re: one more ConfigUI level

Matt,
the increase/decrease value is a great idea!
That would solve most of my challenges as some displays depend on more than one input value (e.g. device and expert mode vs plot and expert mode)

I have indigoplot running as a device - it was actually very easy just changed some validatePrefsConfigUi to the device equiv.
But I don't use any device functions yet. Still doing all data management myself..

Thanks

Karl

Page 1 of 1

Who is online

Users browsing this forum: No registered users and 5 guests