@Steve_Block wrote:
This is the method I got to work, but it is too messy for practical use and does not look standard compared to all the other windows. Can't NI just add this as a built in feature to the subpanel control?
I'm sure they could, but you would have to justify the need. Personally, I can't say I have had the need.
In any case, the only "standard" I know of is using the OS parenting functions to define windows as children of other windows, and I'm having a hard time coming up with programs which actually use this. Office used to do it, but they stopped quite a few versions ago (except maybe for comparing documents)? There are programs which do this for floating toolbars by setting them to be modeless windows (and that includes things like the context help in LV, although I don't think that's actually set as a child of any window), but those are generally used as helper windows, not as the actual content. When I think of things like the tab grouping arrangement window in Firefox or the multiple panes in Blender, those are set up using custom code.
Anyway, you can certainly call the code as a separate VI and then set that VI window to be a child of your window, and then you won't need a subpanel. You should be able to find examples by searching for MDI.
Otherwise, it should certainly be possible to wrap up the subpanel in an XControl or hide its handling code in brat VI and I have seen multiple examples over the years of people doing this, including things like minimizing and restoring. That way, your calling code stays simple.
___________________
Try to take over the world!
