Add Data layer for VIs in addition to Front Panel and Block Diagram, because not all data needs to go onto Front Panel (user interface).

[Yakov]

The problem:

We have a Front Panel and Block Diagram for each VI.

Front Panel as of now serves two purposes:

* User interface

* Data declaration/container

EVERY time I have a VI that has user interface, I have to hide data elements (controls/indicators) that do not belong on user interface outside the front panel boundaries.

EVERY time I need to add/edit any data element I have to move the front panel to get to my hidden data. (Then you know what happens, right? You build the application, run it to find out that you forgot to shift the user interface back, and your application shows data guts of the VI instead of neatly arranged user interface portion of the front panel)

My suggestion:

VI should have three layers:

* User interface

* Data

* Block Diagram

Then you can edit your VI's data and block diagram all you want, and never mess up your user interface.

Data elements on the data layer don't need to have all that heavy 3D graphical representation where only borders of your nested data structures take up half a screen.

Each data element may or may not have graphical representation on user interface.

What do you think?

[altenbach]

The same issues are also addressed in my unused items tray idea. (Except that it applies to the front panel AND block diagram and is thus more universal).

At edit time it should typically be collapsed. At debug time it should be possible to show the front panel version as some kind of "super probe window". At run time, it should be completely hidden.

[Darren]

Any idea that has received less than 7 kudos within 7 years after posting will be automatically declined.