merging FP of children class

[elset191]

---

tst wrote: 

Like I said, this was a quick and dirty example. It's extensible easily enough (you simply add more classes to the hierarchy), but I think I would prefer having the listbox, if only because it can simplify the code, because it can allow you to "check out" the object once at the start of the config VI and check it back in when you finish or switch to another VI. With all the VIs being displayed at the same time, you have to check out the object for every modification.

---

Theoretically, one could hide the list box and say, use tabs to select different classes, similar my earlier example, ya?.  Say, put the subpanel on top of the tab control and just switch what's loaded in it as the user selects new tabs.  This would obscure the fact that he's actually traversing a class hierarchy.

[elset191]

---

@elset191 wrote:

---

tst wrote: 

Like I said, this was a quick and dirty example. It's extensible easily enough (you simply add more classes to the hierarchy), but I think I would prefer having the listbox, if only because it can simplify the code, because it can allow you to "check out" the object once at the start of the config VI and check it back in when you finish or switch to another VI. With all the VIs being displayed at the same time, you have to check out the object for every modification.

---

Theoretically, one could hide the list box and say, use tabs to select different classes, similar my earlier example, ya?.  Say, put the subpanel on top of the tab control and just switch what's loaded in it as the user selects new tabs.  This would obscure the fact that he's actually traversing a class hierarchy.

---

Actually that probably wouldn''t work, because you would need to add tabs dynamically depending on how deep the hierarchy is.  I doubt that's possible..

[JackDunaway]

---

@elset191 wrote:

Actually that probably wouldn''t work, because you would need to add tabs dynamically depending on how deep the hierarchy is.  I doubt that's possible.. 

---

You could dynamically populate an array of strings that were customized to look like tabs...

[F._Schubert]

I'd use a ring or a combo box.

BTW: Very interesting idea.

Felix

[tst · Accepted solution]

I really don't see the advantage of tabs (real or simulated) for something like this. Tabs expand your list horizontally, which is DEATH when you have a text list. That's why tab controls either add rows or have next and back buttons when you have more tabs than the width allows. Both are inelegant. The listbox (or the ring Felix suggested) are cleaner. I would probably prefer the listbox, although I have used a ring on PDAs, which have limited real-estate.

I did modify the example I uploaded to use a listbox, though (it's quite simple), and I actually agree with you that the experience is not particularly convenient and that the single UI which appears in the example is more user friendly. This is actually unfortunate, because it's a lot less programmer friendly. At some point, that would have to be reconciled somehow (maybe by using VI activation events to recognize the move between subpanels or something similar).

[tst]

This discussion is about to be expanded here. I suggest you follow that thread and the thread it links to to see how this develops.