LabVIEW Idea Exchange

Hi,

I can't find the reason why the users have to declare or not the writing of the configuration file.

Usually, if you want to write into the file you have to declare it at the beggining when you opening the file. Then when you closing you just disposing the reference. That is the default thing for all language environments. So why complicating the thing?

It causes a lot of hidden problems because it usualy work on the development machines and on the deployment machines it doesn't work as the folders in Program Files are usually read only. That makes the debugging difficult and itself is unnecessary problem.

Usualy, users know upfront  what for they are opening the files, so why ask them at the end instead at the beggining? Additionaly, the Open Config Data.vi is testing indirectly the writeablity asking for creating the files if necassary,

 so again, why to declare it at the end?

Hi,

I think it'd be better if NI would allow some ordinary VIs (the good group for example is the 'triangle VIs) to be verically orientated like this:

or like this:

Of course the symbol of the operation needed to be not rotated for securing easy readibility.

Main advantage: saving the development space in horizontal dimension.

Other advantage: better visibility.

No disadvanteges in my opinion

When using clusters, it's normally necessary at some stage to unbundle or bundle. The block diagram could be made cleaner if cluster terminals could be expanded by the user to show bundle and unbundle terminals, basically by incorporating the current 'unbundle' node. The diagram below illustrates this.

Additionally, this makes it much tidier when trying to modify an element in a cluster. In the picture below, the top image shows the current method and the bottom one shows the proposed method:

It might be that there's already a way to do something like this but if there is I don't know about it!

The sequence locals in a stacked sequence structure appears on the right side, both in the parent frame and in the other frames. It'll be nice to read from the sequence locals if it appears on the left side in the frames which reads values from it and right side in the frame which write to it.