Jim Kring

Paul: I would recommend talking to NI about this one. It is probably an issue with LabVIEW talking to the Linux sound system.

LabVIEW for Everyone includes the evaluation version of LabVIEW for Windows (but not Mac OS X or Linux) since this is the only evaluation version available from National Instruments. The most likely reason that there is not an evaluation version for Mac OS X or Linux is that these platforms do not support the product activation technology that is used by LabVIEW. As Chris (crelf) mentioned, your best bet is to download the latest evaluation version from NI's website and/or to discuss your platform specific needs with them.

Looks like a VI hierarchy to me :-)

I would like to wish PJM_labview congratulations on becoming a Certified LabVIEW Architect. With years of great contributions to LAVA, we knew you could do it. :beer: :thumbup: "Pass on what you have learned." --Yoda

Here's a yahoo news article. And, here's the Microsoft Robotics Studio website. OK, but can they control LEGOs?

I agree that we need these suggested features.

> I'm a LAVA, not a fighter We LAVA you too, Chris!

The book is in the final stages of production, now, and should be hitting the press, shortly thereafter -- we have worked very hard to ensure that it would be out before NI Week. Also, it's going to be pretty thick (~1000 pages -- see, Mike, I did add weight to the book ), so you will have something to read on the flight home, too

Chris, A preemptive congratulations on your 500th post. Cheers,

I also like to label my For Loops using a For Each syntax that reflects the array elements that I am iterating over. For example: For Each Device For Each Config Section For Each Config Key For Each File This allows one to quickly understand the intent of the loop. I sometimes take it a step further and describe the work that is done inside the For Loop, such as: For Each Device: Initialize Device For Each Config Section: Get Key Names For Each Config Key: Read Key Value For Each File: Get File Date and Delete if Old If there is more work than can be describe in a single statement, I make sure to comment each block of work inside the For Loop. The same sort of thing can be done for While Loops. For example: While TCP connection is valid: Read TCP Data While No EOF Detected: Read Line from File Cheers,

Chris, OpenG Builder does work under LabVIEW 8.0. Cheers,

File Name: JKI Fast Mass Compile Tool File Submitter: Jim Kring File Submitted: 20 Jun 2006 File Updated: 22 Oct 2006 File Category: LabVIEW Development Environment This has dropped the 8.0.1 mass compile time down from a range of 4 to 8 hours to about 30 to 45 minutes. Rumor has it that NI Field Sales engineers are recommending this tool to customers who are applying the 8.0.1 patch.. Click here to download this file

Yes, it is to create a global, named semaphore. The reason that the test for a valid semaphore reference is useful, is because the reference will go invalid when the top-level VI in the call chain that created it goes idle (stops running). This makes testing components (by pressing thier run buttons) possible, rather than requiring that the entire application be running.

Now that you have found that, all you need is a VI that recursively in-lines all subVIs. You should be able to use the resulting sequence structure reference to traverse for subVIs. Want an easy way to traverse? Just use <LabVIEW 8.0\vi.lib\Utility\traverseref.llb\TRef Traverse for References.vi>. Cheers, -Jim

I'll take some hair, while you're at it.

1 NI Week ticket: $800 1 Round-trip ticket to Austin: $400 1 week's hotel and accomodations: $1000 Sitting with your LAVA buddies at the keynote... priceless

Welcome, jdebuhr! I'm sure that I speak for most when I say that we look forward to your participation in the LAVA community

Chris: Glad you like the se-radio.net podcasts -- I'm enjoying them too. Mike: Regarding, calling LabVIEW from Python, here is some example code that I through together a quite while back. Cheers,

Steps to Reproduce: 1) Start with one item selected in a listbox (see next figure). 2) Press (and hold down) <Shift> key and (with the <Shift> key still pressed) left-mouse-click another element of the listbox. This will cause the range of elements between the initial and final to become selected (see next figure). Continue to hold down the shift key. 3) With the <Shift> key still pressed, move the mouse cursor in any direction. Observed Result: only one element is now selected

Steps to Reproduce: 1) Left-click on an element (see left figure below), continue to hold the mouse button down, drag the cursor to another element (see right figure below), and release the mouse button. Note that the mouse-down event was on element "three" and the mouse-up event was on element "five". 2) Press (and hold down) the <Shift> key and (with the <Shift> key still pressed) left-mouse-click another element of the listbox (see figure below). Observed Result: The range of element between the initial mouse down element ("three" of step #1) and the <Shift>-clicked element ("seven" of step #2) become selected (see figure below). Expected Result: The range of element between the final mouse up element ("five" of step #1) and the <Shift>-clicked element ("seven" of step #2) become selected (see figure below). Final Thoughts: It appears that the shift-click range.start is being defined by the mouse-down location, rather than the selected item. If it has to be associated with the mouse (rather than the selected item) then it should be associated with the mouse-up, rather than the mouse-down location.

Ben, There is an interesting article that I think you will enjoy, which is called "A Group Is Its Own Worst Enemy". It examines how free discussion will inevitably digress to the more base subjects and how groups need to organize themselves in order to overcome such entropy. :beer: Cheers, Jim

Colin: You speak of "partnership" repeatedly. So, what has NI done (or is NI planning to do) to partner with LAVA and other independent LabVIEW resources? There are several NI employees who do provide regular high-quality contributions to LAVA, in the form of forum participation, and I think that's great. However, I think that NI could do a whole lot more. Also, NI needs to realize that we are not very interested in partnerships that co-op our efforts for NI's direct benefit.

OK, that's new for LabVIEW 8.0. It's really starting to frustrate me how many of these hidden little gotchas NI has started putting into primatives. Adding right-click options to nodes is such an awful way of circumventing the 4-2-2-4 conpane standard. At least with Search and Replace String the function icon looks slightly different (having an RE "pattern" asterisk), but the Read Text File function has similar options for conveting EOL characters and this just drives me nuts. Who is going to think to right click on a node to see how its configured? These are worse than Node Setup Options. A firm wag of the finger to whoever decided to add right-click options to nodes, especially without any distinct visible change of the icon

Henning. Search and Replace does not use regular expressions. Also your interpretation of \s and \t is not correct, with respect to their usage in regular expressions: \s is the space character (not all whitespace) \t is the tab character \n is the line feed \r is carriage return ...and, there are some others. Please see the attached example, which meets your requirements. Download File:post-17-1147276416.vi Another (and probably best) option is to use Search and Replace Pattern.vi.

Use the regular expression "[\s\t]+" to find the next instance of one or more consecutive space or tab characters. Do this in a loop with a shift register until you've replaced them all.