LabVIEW Idea Exchange

In vi.lib\Utility\file.llb the 'file open+.vi' throws an error when a file can't be opened. It doesn't tell which file it can't open.

One of the strenghts of LV is the source string in the error cluster that can be used to include a lot of extra information. For example which file couldn't be opened.

The change can be very simple, just add the file into the source string, also see attached file:

This is probably true for some other files here as well.

(also checking out these files... would be nice if they are updated to some newer standards... still some very old styling here...)

Some background: https://forums.ni.com/t5/LabVIEW/Looking-for-feedback-on-the-Carya-PDF-toolkit/m-p/4229342#M1228046

As discussed initially in this thread, I'd suggest that folders in the Project Explorer do not automatically expand to reveal their content when dropping an object in them. It could be a possible behavior, but not the default one, which is VERY annoying. A possible behavior would be that of the Windows Explorer (PC) or Finder (Mac) folders:

- drag and drop an object: it will disappear in the folder

- drag and hold the object over the folder for 1-2 s and the folder will open up. You may or may not drop the object in it. If you don't and move on to another folder or location, the folder should revert to its initial state (closed in this example).

Check the thread I refered to above for graphic details (if I may say).

Thanks.

VI Analyzer has a "Error Cluster Wired" check, that does a great job of helping to find instances where you (accidentally) forgot to wire up the error out of a item on your block diagram.

Unfortunately, it only considers "Nodes" on the block diagram, and ignores tunnels through structures.

So you get problems like this:

Where it won't notify you about not connecting the error tunnels (any flavor of tunnels, only shift registeres shown).

I'd like to see VIanalyzer Error Cluster Wired check to include ability to check for error tunnels (inside or outside terminal) in structures wired:

When working on a large project I sometimes want one of my subVIs from some where else within the same project.

I then have to either find it in the long list of VIs in the Project Explorer window (if I remember the exact name) or navigate through my code to find it and drag it into the location I am currently working.

How cool would it be if there were a Current Project subpallet that contained all the VIs being used in the current project (minus the NI VIs).

Something like the view in the pallet of the Find window's Select Object:VIs.

I have heard of users getting something like this by putting their project in the user.lib folder.

mck

I know you can mix fonts on a string control but I would like to mix fonts
on boolean text.  Example: When the button is false, is says "OFF" in font
25.  When the boolean is true it says "ON 23" with "ON" in font 25 but the
"23" in font 12.

Whenever I download a new toolkit or example, if I don't know where a function block on the palette is located, I have to use the search or fumble through the palettes to find it.  It would be really helpful if there was an option when I right-clicked a function that would pop up the functions palette to show where it is located.

I have run into the problem from time to time that I create a new build specification in my project, hit the Build button in the setup dialog just to have the build hang or crash LabVIEW. To add insult to injury when I opened the project file again (sometimes even after recovery) that new build specification was not there since the project was not saved before building.

I have now trained myself to resist the temptation of hitting that Build button. Instead I will exit the dialog, save the project and then start the build via a right click.

I would really like to see the project file being saved before the build is executed.