Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation


About mplynch

  • Rank
    LAVA groupie

Profile Information

  • Gender
  • Location
    Tullahoma, TN

Contact Methods

LabVIEW Information

  • Version
    LabVIEW 2013
  • Since

Recent Profile Visitors

641 profile views
  1. I probably just didn't land the right search terms to find it, but I've had little luck locating any technical information on the performance of using Generate User-Defined Trace Event calls. Is there any world in which it's a good idea to leave them in code just in case you need it later? I'm interested in best practices here. Another idea was maybe to use a conditional disable structure to ignore the code if a flag is set. Is it worth all that effort, or is it fairly innocuous to just leave the calls in and take whatever (perhaps small) performance hit? Are ther eany other recommend
  2. You're absolutely right: that's what you fine folks are for! The question was academic... just trying to learn!
  3. Doh! That was stupid. Of course, you're right... Still curious about the best practice/efficiency bit... Oh, and I totally made up that name. I don't know if there's an official term for it. Either way, you seem to have understood what I meant, so I stand by it!
  4. Is there a performance difference between implicitly and explicitly linking a property node to a control or indicator? I tend to use the explicit variety unless I'm getting a reference to a control/indicator as an input to a sub-VI. I'm curious if that's considered good practice. Also, when using the explicit variety, does LabVIEW handle cleaning up the control/indicator reference? It's my understanding that if you create a reference to pass to an implicitly linked property node you need to close it to free up the reference. I haven't been doing that with the explicit nodes since the w
  5. Jacobs has multiple full time software engineering opportunities in our Bingham Farms, MI office. We're looking for an independent, capable developer who can also represent our team with clients, particularly in the Detroit area. This is a unique opportunity, offering the chance to work in many varieties of test facilities such as aerodynamic or climatic wind tunnels, component test stands, automotive test facilities, air craft engine test facilities, structural test stands, manufacturing validation test stands, etc. We support automotive clients such as Ford, GM, Honda as well as aerospace
  6. That certainly cleans things up a bit. Great suggestion!
  7. Thanks for the suggestion! I wish I knew what the Big-O was for the Sort Array VI, as the only other worry I have is what will happen when the list grows. I did some quick profiling with it, and it seems like it's O(n^2). I guess I'd better just limit the uses of this sort of editor to instances in which the listbox size will remain relatively small. Attached is a working example, both in LV2013 and 2009 for posterity... Sorted Listbox Example.vi Sorted Listbox Example LV2009.vi
  8. In the attached VI, I have an editor of sorts which permits the modification of a list of strings. There is a listbox which displays the list in sorted order, and a text box used for modifying the currently selected item. I'm struggling with determining the best approach to maintain selection in the listbox after sorting takes place. The only solution I've really come up with is to do a linear search for the new value in the listbox's ItemNames array and set the listbox's value accordingly, but I'd like to be able to allow duplicate values. In that case, the search obviously creates some od
  • Create New...

Important Information

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