Leaderboard

Not sure if anyone else has seen these but I thought they are awesome! This is Engineering This one even has LabVIEW in it!!! ENGR Nights

Just out of interest, I've kept tracking these two ideas. The current score is 119 - 110, an entertaining basketball game, albeit with poor defence! What's interesting is that (a) there was only a small kick to the ideas after posting here in mid-December, and (b) they still appear to be fairly synchronized in their popularity.

"With over 900 years of motorbike building prowess behind them Triumph have created two wheeled motorbike classics." "Argument juice is added from the argument lobe of the female brain allowing the finished bike to change direction in an instant."

The main reasons are probably cleanliness, code safety and efficiency. A variant will cause a data copy, which is not a big deal if you're comparing a boolean, but could be an issue if it's an array with 10M elements. If you also make all your VIs work only with variants, then you will either start getting variants in the BD or the user will be forced to repeatedly convert back (and possibly make mistakes). In the end, if you create a tool which will be reused many times, it takes considerably less effort to make it easy to use upfront than it does to make it simple to build. If you create an automated tool to help with the polyVI creation, then the effort becomes even more minimal. The real thing we need here is for LV to be able to automatically adapt VIs to work based on input type. NI has known this for years, but so far hasn't managed to come up with a stable and reliable mechanism. Hopefully at some point they will and then we won't have to deal with this any more.