03-15-2006 11:16 AM
03-15-2006 11:21 AM
03-15-2006 11:26 AM - edited 03-15-2006 11:26 AM
Message Edited by altenbach on 03-15-2006 09:28 AM
03-15-2006 11:36 AM - edited 03-15-2006 11:36 AM
Y'all have me recalling an old Saturday Night Live skit where they were spoofing "Leave it to Beaver".
Beaver was depressed over something and says "If I had a gun I'd shoot myself!". Eddie Haskle responds "Here Beav, you can borrow mine."
When I face code like that described above I'd just start editing VI icons with B&W text to be able to decypher what I am looking at. I usually continue that until I finally decide to just throw it all away and do it right.
Ben
Message Edited by Ben on 03-15-2006 11:36 AM
02-01-2007 03:36 AM
02-01-2007 03:46 AM
10-04-2009 01:37 PM
Hello,
From http://zone.ni.com/devzone/cda/pub/p/id/347
The LabVIEW compiler performs compile-time inlining, but you also can force inlining in the development environment by adding the line “inlineSubVIEnabled=TRUE” to your LabVIEW.ini file. Once you restart LabVIEW, a new item called Inline subVI appears in the right-click menu of subVIs on block diagrams (see Figure 4). Selecting this item moves the code from the subVI into the calling VI, effectively the reverse of “Create subVI.” This feature does not usually make for the most attractive code and removes several often important features of using subVIs – including modularity, encapsulation, and scalability – but it is a handy shortcut if you need to force visibility in the development environment.