Darren's Weekly Nugget 08/08/2006

Darren's Weekly Nugget 08/08/2006

Post by Darre » Thu, 10 Aug 2006 00:40:08


As of this morning, <a href=" http://www.yqcomputer.com/ " target="_blank">LabVIEW 8.20</a> was officially announced at <a href=" http://www.yqcomputer.com/ " target="_blank">NI Week 2006</a>.  I am going to use the next few Darren's Weekly Nuggets to describe some features I personally added to LabVIEW 8.20.  These are the kind of features that (hopefully) make people say, "Whoa, cool!", yet aren't quite big enough to make it as bullet points on marketing material.
 
For starters, I'll mention the Remove Breakpoints from Hierarchy utility that you will find in the Edit pull-down menu of any open VI.  Selecting this menu option will remove any breakpoints you have set in the current VI (i.e., the VI from which you selected Edit > Remove Breakpoints from Hierarchy), along with any breakpoints in the current VI's subVIs.  A summary dialog then comes up and indicates how many breakpoints were removed from each VI in the hierarchy.
 
I've seen this feature request a number of times on the NI Discussion Forums, so I hope the word gets out to everybody who has wanted this feature in the past.
 
-D P.S. - Check out past nuggets <a href=" http://www.yqcomputer.com/ ;message.id=1669" target="_blank"> here</a>.
 
 
 

1. Darren's Weekly Nugget 08/21/2006

2. Darren's Weekly Nugget 08/28/2006

Here's an obscure one for everybody.  The In Range and Coerce function (Functions > Programming > Comparison palette in 8.0 and later) takes many different datatypes as inputs.  One of the datatypes it accepts is a path.  Prior to LabVIEW 8.2, the In Range and Coerce function would always return False for its "In Range?" output if you wired paths as inputs, no matter what the values of the paths were.  In LabVIEW 8.2, however, the function can actually do something with paths.  Specifically, it will check the ASCII values of the path characters and indicate whether or not the input is within the specified range.  Check out this screenshot:
 
 
 
As you can see, the value of "c:\blah4.txt" is determined to be "in range", i.e. in between the values "c:\blah1.txt" and "c:\blah5.txt".  I don't know when I would possibly use this behavior, but it's nice to know it's there.
 
-D P.S. - Check out past nuggets <a href=" http://www.yqcomputer.com/ ;message.id=1669" target="_blank"> here</a>.


In_Range_Coerce_8_2.jpg:
http://www.yqcomputer.com/

3. Darren's Weekly Nugget 08/14/2006

4. Darren's Weekly Nugget 01/08/2007

5. Darren's Occasional Nugget 08/14/2008

6. Darren's Occasional Nugget 08/11/2008

7. Re : Darren's Weekly Nugget 11/20/2006

8. Darren's Weekly Nugget 09/05/2006

9. Darren's Weekly Nugget 10/30/2006

10. Darren's Weekly Nugget 06/12/2006

11. Darren's Weekly Nugget 07/10/2006

12. Darren's Weekly Nugget 12/11/2006

13. Darren's Weekly Nugget 10/09/2006

14. Darren's Weekly Nugget 05/22/2006

15. Darren's Weekly Nugget 11/06/2006