Leaderboard

Hello, happy new year! My customer produces thousands of parts within the last weeks and at every part I do about 3 SQL statements. No error untill now. It seems to work perfectly with the updated version of your library! Great work! Regards Matze

Okay, I had to create an account to answer this. My company uses this stringent requirement to part number everything, including each individual class. As such, each class folder contains its part number. There have been plenty of occasions where the number I get is already used and I wasn't informed until after the class was developed. As such, I can and often do have a class and around 50 Vis that I'd have to move. I use to try by windows explorer, but could never get it to be pretty. Then I discovered the Files view. Original view: In here, I select the class and all its member VIs. Right click, and Select "Move on Disk..." I then find where I want to move it to, create folder if necessary, and select "Current Folder" It'll take LabVIEW a few seconds to process simple moves, to about a minute for really complicated ones. It also relinks every VI call. (If in memory) Afterward, it shows properly as moved: This has literally saved hundreds of hours vs trying to move each individual VI one at a time. We also compile our code into lvlibp libraries so other functions that would call it, calls the packed library instead. That's why we won't have issues with external "non-loaded" code attempting to find new location.

No. The issue is that the connector pane's terminals have to be connected to controls/indicators on the front panel, so if you want to get data in/out through the connector pane, you need a front panel. If the connector pane and front panel could be decoupled, then most VIs wouldn't even need a front panel. But they aren't, so we're stuck with them. Maybe post on the LabVIEW Idea Exchange. Yes! I think VIs should have n front panels (where n could be 0). Think of a lot of websites: they have different "views" based on the client that's connected to them (desktop, mobile, etc). I think being able to define something similar in a VI could be helpful. Imagine a VI running on an RT system - you could have different front panels for different user security levels, client types, and more.

Take a look at this PDF Tookkit for LabVIEW I use Cute PDF to create pdf non programatically Hope that helps