Oh yes! Currently, if you need a "dynamic" number of subpanels, you have to create a bunch of them and then move the ones you don't use outside the visible FP window area.
Would be easier to make them invisible programmatically.
Oh yes! Currently, if you need a "dynamic" number of subpanels, you have to create a bunch of them and then move the ones you don't use outside the visible FP window area.
Would be easier to make them invisible programmatically.
You can make them invisible. Just use their Visible property, like any other control.
In general, I think that this idea doesn't apply specifically to subpanels, but to any control with a 3D border. I'm not sure how I feel about the idea. On the one hand, it seems reasonable. On the other hand, I don't think I have any real use case for this. Even for scripting, I would probably simply create a custom control and drop that.
Subpanels with invisible frames are themselve completely invisible without a vi front panel loaded in them. That is very anoying for development as you never know where they are. In a compiled application it looks nicer when the subpanel frames are invisible. With many subpanels, it is a lot of clicks to make each subpanel frame invisible each time I want to build my application.
Because the property is not available through vi server I cannot automatize the process.
Generaly speaking, I find it always anoying that some properties of controls are only available through the context menu, but not through the vi server property nodes (like color of some elements of controls).
This Idea is restricted to make the property available throught a property node.
Argh! I understood it as a SubPanel didn't have the Visible property, but of course it does. This is what it's missing, and in that case my kudo still stands:
This idea would make it easy to find ones SubPanels in edit mode even when the frame is hidden, if that idea was implemented with not only looking at the Visible property, but also special cases like SubPanels with hidden frames for instance.
Resurrecting this. I'm working on a OOP custom array framework and to simplify usage I've got a VI that's part of the framework that contains the necessary number of subpanels for the array elements. This vi can be cloned an inserted into subpanels created by the app developer. I'd like to be able to pass in whether or not to make panel borders visible.
For now the route I'll go is to turn off all borders and if I want the appearance of borders I'll just put them as decorations in the facade VI of my element panels.
