LabVIEW Idea Exchange

I am sure many do this:

• Use an enum and hide the tabs
• Programmatically change page when enum changes

This works great, but during development the page obviously does not change when changing the enum. Either you right-click the border of the tab control and "Go To Page" or you display the Page Labels Display (and programmatically hide it) or something along these lines.

But why not make the tab control's Page Labels Display an enum in the first place? Being able to customize it would be great, but just making it an enum would be really helpful.

So basically:

• We get the look we want
• We avoid having the extra event to change page during runtime
• Page also changes during development
• Everyone is happy

This one has irritated me for a long time.  When I create installers, I like to utilize the welcome dialog so the user knows exactly what they are installing.

But the application builder limits this to 7 lines of text.  Look all the unused space!

My suggestion:  Make use of the unused space and let us specify more than 7 lines of text.

TestStand provides the extremely useful Label step type.

It would be extremely useful if the LabVIEW Project Explorer provided a similar Note project item. The Note would serve as a documentation and annotation tool inside the project. Project notes would serve to explain the purpose of a group of lvlibs or lvclasses, or to provide short descriptions inside an lvlib, lvclass, or virtual folder.

As a workaround I currently use virtual folders to add notes to the project. By convention I name these virtual folders starting with "_Note:". The underscore helps the Note appear first (near the top) when the items are arranged by Name or by Type. By convention I never add any item inside the _Note virtual folders.

The implementation of a Note item could be quite simple. A Note item would essentially be just like a virtual folder with the following modifications:

• Different icon. An icon that resembles a document would make sense.
• The Note item would not be able to contain any other items.

Currently the only way to set/modify Tcp socket options is by directly calling some system library, as done for example in this post.

This not only causes code difficult to understand ("what does that library call do again?") but also poses problems when you want to use your code on different operating systems: Currently the only way to do this is using "conditional disable structures", and then Labview still tries to load the code used for a different operating system...

Labview should have a standard way to set socket options within Labview code, at least for the most important options (Nagle algorithm leaps to mind...). This could either be done as additional inputs to the "Tcp open connection"-VI, or (much better) using property nodes for Tcp connections.

It's a common convention that the space bar is used to pause/un-pause videos that are playing. It would make sense to me that pressing the space key would toggle the pause button (Pause / Continue).

1) Pressing Space Bar key would be the same as pressing "Pause" on the VI toolbar.

2) Pressing Space Bar key again would "Continue" (un-pause).