Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Darren

  1. Hi John, I don't have a way to copy the "attributes" from one control to another...it seems you would just need to create a VI that uses property nodes to get/set all the appropriate properties of the controls. As for the tree contents, I wrote this VI a while back that will duplicate the contents of one tree control into another. It's attached below, saved in LabVIEW 8.0 format. Let me know if you have any feedback, since I plan on shipping this VI in the vi.lib\tree folder in a future LabVIEW release... Hope this helps, -D Download File:post-4441-1169769387.vi
  2. I posted a VI Analyzer test on the NI Discussion Forums that will detect any terminal on the diagram that is a Variant data type that also has a coercion dot. See here. -D
  3. Hmm, apparently I didn't quite grasp the effect my retirement from nugget-writing would have on the LabVIEW community. You guys go ahead with whatever plans you make for writing your own nuggets, but as you can see here, my retirement lasted all of a week. Yes, the nuggets will still be (occasionally) cooking... -D
  4. Ah, ok. In that case, I don't know of anything you can do other than to extract each item out of the serial string and cast it to the appropriate datatype, then bundle all of those individual items into a cluster. I don't think you would be able to use Unflatten from String directly because the string data doesn't directly correspond with a cluster datatype containing all those elements. -D
  5. Are you looking for the Bundle By Name function? That seems to be what you could use to replace all the other code in your VI. -D
  6. Make sure to let NI support know that it's not actually a bug, but an error in your code. -D
  7. The string you're generating for the Value of the tree is incorrect. When the value goes down to 1, the text you display in the tree is "Cycle A - 1 execution", but if you probe the string you're wiring into the Value property, it is "Cycle A - 1 executions". Since this is not a valid tree tag, no line is selected. Also, I would recommend keeping an array of the tag names assigned to each row in the tree, and changing the Cell text for a row as it's changed, instead of re-writing the entire contents of the tree every time the number for a single row is changed. -D
  8. Yes, this method is handy. It's only available in LabVIEW 8.0 and later. If you need this functionality in LabVIEW 7.x, there's a VI that does exactly the same thing in vi.lib\tree. -D
  9. Maybe that has something to do with the fact that LabVIEW is way more comprehensible than C++? -D
  10. From the LabVIEW 8.2 Online Help for the And Array Elements function: "Returns TRUE if all the elements in Boolean array are TRUE. This function also returns TRUE if Boolean array is empty because TRUE is the identity for the Boolean AND operation. Otherwise, the function returns FALSE. This function accepts an array of any size but returns only a single value based on all values in Boolean array. " I remember asking this question a while back...I think lots of people have asked it in the past, which is probably why that sentence is now in the Help. -D
  11. I wanted to add some File I/O Utility VIs to the palettes in LabVIEW 8.2 that would be helpful for all to use...and I didn't "borrow" that idea from anybody. That being said, in my original version of Check if File or Folder Exists.vi, I did return an error on empty path. However, one of my fellow developers in LabVIEW R&D (a Linux guy, no less) filed a bug report against the VI because of the reason Jim described...empty path means "/" on Linux, "My Computer" on Windows, etc. So now the VI functions correctly in the technical sense. I will file a Documentation CAR against the VI so
  12. I tried, but when I used the "Quick Search" and put my address as Austin, TX, 78727, it gave me back an empty Lat and Long. -D
  13. Yup, I didn't realize the item names were carried along the wire after an Unbundle. LabVIEW's too smart for its own good! Since this is the case, I agree that jpdrolet's approach is the best...I just tried it and it works. -D
  14. The easiest thing I can think of is to unbundle the cluster elements, then re-bundle them with a Bundle function, with no datatype specified on the middle terminal. This should remove label names from the cluster data, leaving you with only the data types. -D
  15. Darren


    Yes, the mis-capitalization of LabVIEW bugs me a lot, too. Although, I've heard from one of my marketing contacts that editors of technical articles (not written by NI) are notorious for refusing to capitalize it properly. Apparently one of the more popular, intentional, mis-capitalizations is "LabView"...they don't want the last half in all caps because it seems like an endorsement. ??? Don't ask me, I just work here. Although, I'm guessing those same editors also print "Matlab" instead of "MATLAB". -D
  16. The difference that I can see is that the submitted code runs 3-4 times faster than the Sort 1D Array approach. -D
  17. LabVIEW R&D is already aware of this issue (CAR 3ZPEL5X1). You should see it fixed in a future LabVIEW version. -D
  18. Actually, I'd prefer if somebody translated it into LabVIEW...I could probably understand a square meter of LabVIEW code better than that text-based nonsense. -D
  19. If you're already got your left hand on the Ctrl key (which I almost always do when programming in LabVIEW), it's pretty quick to do Ctrl-E -> Ctrl-W. That's the procedure I usually do when wanting to close a VI while viewing its diagram. -D
  20. One time when I was teaching a LabVIEW class in California, I had to go to a ghetto car rental place (the only place open on Sunday that would rent a car to a 23 year old). I gave the guy my corporate credit card and he said, "National Instruments...what are you, some kind of musician?" -D
  21. Look closer...I believe there's a candle directly behind the middle one...if you look at the flames above the middle candle, you'll notice there are two flames going in opposite directions...I think one of them is from the "hidden" candle. -D
  22. We're aware of the issues regarding installing multiple toolkits to different LabVIEW versions...it's something we're looking into addressing with future versions of LabVIEW and the toolkits. For now, I can direct you to this KnowledgeBase entry which gives a method for installing a toolkit to multiple LabVIEW versions. Good luck, -D
  23. My trick for installing the SPC Toolkit is to copy the installer to my local hard drive and run it from there. Using this method, I have installed the SPC Toolkit to Windows XP with LabVIEW 8.2 with no problems. -D
  24. And here's a link to one of my Weekly Nuggets on the NI Discussion Forums where I talk about customizing the connector pane of new VIs in LabVIEW 8.0 and later. It also includes a VI that returns the proper 4-digit connector pane ID given a specific pattern. http://forums.ni.com/ni/board/message?boar...ssage.id=171666 -D
  25. Perhaps not, since the functionality of that VI is accomplished with a VI that is already in the LabVIEW shipping palettes (see my previous response): -D
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.