Leaderboard

I presented at NI-Week 2009 on a couple of paradigms for extending the LabVIEW Error Handling Core (as inspired by all your posting here). Here are the resources from that presentation (I didn't screencapture the examples, but you should be able to see what I was talking about from the video and the code that's included): NIWeek Session Video Presentation Slides.pdf Presentation Code.zip It's a hot topic, and I know a lot of people have strong opinions on it, so let's discuss!

When I double-click a VI's icon in the top right corner and I have the front panel open, LabVIEW opens the icon editor without complaints. But when I do the same from the diagram LabVIEW opens the icon editor and it also complains by beeping. Why? Is it ticklish?

Aha. Sounds like you've reached the PCI bandwidth limitation, which is about 133MB/s max and about 110MB/s sustained. Not a lot you can do about that except change the motherboard for one that supports PCIe. PCI = 133MB/s Max. PCIe x1= 250MB/s Max. PCIe x4 = 1GB/s Max. PCIe x8 = 2GB/s Max. PCIe x16 = 4GB/s Max.

Make the Splash VI your top level VI and call the Main VI dynamically then use the Notifier trick mentioned above to close the Splash VI. You can also send custom messages to the Splash VI through the Main VI, similar to the Splash screen when LabVIEW loads thus informing the user as to what the application is doing. This gives a feeling to the user that the application is doing something in the background rather than just a splash screen.

I like this tool I have made some small modification to it. Now dirs of vis can be recolored (and with recursive also). Modification require openg file tools. I attach the file to message. Hope this will usefull to someone