Jim Kring

Hi Jason, Use Open VI Reference to open a reference to a reentrant VI and you'll get a new clone. You can either open it for use with a Call By Reference node or for invoking the Run method (see screenshot, below). http://forums.lavag.org/index.php?act=attach&type=post&id=5931

QUOTE(Jim Kring @ May 15 2007, 02:21 PM) I have just learned that the above statement is incorrect: apps built using LabVIEW 8.2.1 will run in the 8.2 run time engine. I thought otherwise, due to some strange behavior when testing on a system that had a beta version of LabVIEW installed. See http://forums.ni.com/ni/board/message?board.id=170&message.id=247980#M247980' target="_blank">here for more information. Thanks,

QUOTE(pattousai @ May 18 2007, 01:21 PM) If you decimate (only keep every Nth point of) the y[] array of a waveform, then you will need to multiply the dT (time between points) by N. If you are using the Dynamic Data signal data type, then you can simply use the Sample Compression express VI. Search your palette for "Decimate" and you'll find some functions. One thing to be aware of is that you might want to do some averaging and not plain decimation -- the Sample Compression express VI has an averaging setting.

QUOTE(Aristos Queue @ May 18 2007, 09:40 AM) Sounds simple and elegant. I'll get right on it. Actually, the work-around that I use, is to either employ a factory pattern, where there is a loop (factory) that does nothing but create object references (resulting from a message request and then messages back the reference to the requestor) and never goes idle, or I spawn an asynchronous VI that creates a new object reference, messages it back to the calling thread, and then waits indefinitely, for the reference to go invalid.

Update... [CAR 49EJT400] Status: Reported to NI R&D

QUOTE(BrokenArrow @ May 18 2007, 05:58 AM) Richard: Wiring from the output of the function to the structure frame creates a wire that can be probed. Such wires are commonly left over from debugging activities, where the developer needed to probe the output of a function/VI and had no other need for the data downstream. For example, you'll commonly see the loop iteration terminal wired to the structure frame. http://forums.lavag.org/index.php?act=attach&type=post&id=5901''>http://forums.lavag.org/index.php?act=attach&type=post&id=5901'>http://forums.lavag.org/index.php?act=attach&type=post&id=5901

FYI: We found a work-around, which is to write a string with a single space character to the empty cells.

QUOTE(Herbert @ May 17 2007, 04:53 PM) It is a little know fact that the OpenG/LAVA BBQ started at NI Week 2002 when Richard Jennings invited me to join him and a few other people for BBQ at County Line. That was my first experience with Texas BBQ and the birth of a great tradition.

QUOTE(dannyt @ May 17 2007, 01:53 PM) The Salt Lick is in Driftwood, TX (google map).

QUOTE(Aristos Queue @ May 17 2007, 11:56 AM) No!!!! I have entire software architectures based on exploiting this feature to create objects that are not garbage collected when the call chain goes idle!!! Actually, I'm just kidding, but I'd really like to be able to have more subtle control over the lifetime of references

QUOTE(Aristos Queue @ May 17 2007, 01:15 PM) Salt Lick is great. All the BBQ you can eat Bring more beer than you can drink Capacity for HUGE groups in a semi-private setting Room to park the bus. It's a tradition! :thumbup:

QUOTE(TiT @ May 17 2007, 09:06 AM) Yes, there will be a LabVIEW CAPTCHA on the sign up form (just kidding).

Hi Jason, Thanks for all your hard work on LabVIEW, over the years, and for your great contributions to the LabVIEW community. I'm looking forward to seeing you at the NI Week Community BBQ, this year. Cheers,

QUOTE(Eugen Graf @ May 16 2007, 03:16 PM) If that is an illegal download, then you should be reporting it to NI, not posting it on LAVA.

QUOTE(LvBg @ May 16 2007, 08:21 AM) No, there is no trial version of LabVIEW for Linux (or Mac OS X).

If you cross post to multiple forums, please provide a link to your other posts.

Steps to Reproduce 1) Place a Multicolumn Listbox on the Front Panel of a VI http://forums.lavag.org/index.php?act=attach&type=post&id=5876 2) Right-click on the Multicolumn Listbox and choose: Drag and Drop>>Allow Dragging Drag and Drop>>Allow Dropping Both Allow Dragging and Allow Dropping should now be enabled/checked. 3) Initialize the first column and the third column with some data, using the text tool. http://forums.lavag.org/index.php?act=attach&type=post&id=5877 4) Attempt to drag and drop some of the rows to reorder them. Observed Results Note that you can drag and drop only if you mouse-down on the first or third columns (having text). If you mouse down on the second column (with no text) drag and drop does not work. Expected Results I would expect drag and drop to work, as long as I mouse down on any column of a row that has at least one initialized column. http://forums.lavag.org/index.php?act=attach&type=post&id=5878 Another Oddity... Add some text to one of the empty cells. Now, highlight the text you just added and press the delete key. Try to drag and drop the row containing the cell whose text you just deleted by mousing down on that cell. Note that drag and drop now works when mousing down on that cell. However, it does not work when mousing down on any of the other empty cells (the ones that never had any text). From this last oddity, it leads me to believe that I might be able to work around this bug by initializing the empty cells, somehow. Perhase this can be done by writing empty strings to these cells.

QUOTE(ooth @ May 15 2007, 01:43 PM) I upgraded to 8.2.1, recently, and my visaconf.ini is still in the same old location (C:\VXIPNP\WinNT\NIvisa\visaconf.ini).

Note: This is a cross-post to NI forums. If I have a system with LabVIEW 8.2 installed and I upgrade only the RTE to 8.2.1 (leaving LabVIEW 8.2 installed) will I run into any problems? Will applications that I build in LabVIEW 8.2 still run correctly? Which RTE will applications that I build in 8.2 require? (I'm presuming that the 8.2.1 RTE upgrade will not touch the lvapp.lib stub used by the app builder and that apps built in 8.2 will run in the 8.2 RTE) Here is what I (think I) know: The 8.2.1 run time engine (RTE) is an upgrade to the 8.2 RTE, meaning that the 8.2 and 8.2.1 RTEs cannot be installed at the same time. Applications built using LabVIEW 8.2 will run in the 8.2.1 RTE, however apps built using LabVIEW 8.2.1 require the 8.2.1 RTE and will not run in the 8.2 RTE Has anyone attempted this? Thanks,

QUOTE(crelf @ May 14 2007, 07:46 PM) See this thread: http://forums.lavag.org/Dynamic-Generation-of-Labview-82-Class-Hierarchy-t5673.html' target="_blank">Dynamic Generation of Labview 8.2 Class Hierarchy, This is a modified version of PJM's original

QUOTE(crelf @ May 14 2007, 06:50 PM) Yes, I've heard of such things ;-)

Here are some Numeric terminal icons that I had laying around from working on the book. http://forums.lavag.org/index.php?act=attach&type=post&id=5819

One thing that seems to add noise is the use of text/instant message abbreviations (e.g., "plz u help me") in postings. What do you think about a LAVA ban on text message abbreviations in postings (with the exception of acronyms, which are fine, IMNSHO)?

Here's another thing that I've noticed. EXEs built in LabVIEW 8.2.1 must have the 8.2.1 Run Time Engine (RTE) installed -- the 8.2 RTE will not support 8.2.1 EXEs. Based on past experience, EXEs built in LabVIEW 8.2 should work with the 8.2.1 RTE.

QUOTE(LV Punk @ May 3 2007, 05:20 AM) I'm pretty sure that the answer is "no".