Jim Kring

QUOTE(tcplomp @ Mar 27 2007, 01:44 PM) He also http://forums.lavag.org/index.php?showtopic=7262&view=findpost&p=27344' target="_blank">donated to LAVA, today. He is a very generous soul :worship:

QUOTE(crelf @ Apr 2 2007, 11:09 AM) Ironic self-deprecation works fine, in such instances. And, don't forget that you do get credit for the assist.

QUOTE(crelf @ Apr 2 2007, 04:43 AM) Lots of probing questions, I'm sure.

QUOTE(Jim Kring @ Mar 28 2007, 10:56 PM) April Fools! I just made the While Loop larger than the Block Diagram window and colored the While Loop's frame white :laugh:

QUOTE(alukindo @ Apr 1 2007, 08:07 PM) Personally, I like the reentrant VI clone approach. I recently wrote a little article called http://thinkinging.com/2007/03/29/reentrant-vi-clone-name/' target="_blank">Reentrant VI Clone Name that has some info that you might find useful. Also, in the article's comments, there is a brief discussion of the differences between the *.vit and reentrant VI approaches.

QUOTE(alukindo @ Apr 1 2007, 07:43 PM) This is not a bug, really. It has to do with the fact that a SubPanel is really a control with no value. In order to use it, you need to use it's methods. Since a SubPanel has no data (a null Variant, actually, if I recall), NI has hidden the block diagram terminal (does it even own a Terminal in the GObject model?). When you drop a SubPanel from the palette, I presume that NI executes a little snippet of code (defined in the palette's MNU file) that causes the invoke node to appear. There is no such provision for executing a snippet during copy+paste operations. I know that this is not a great reason that LabVIEW doesn't work the way that you'd expect, but that's how (I believe) everything works.

<shameless_plug>Mike and I will be presenting at NI Week 2007.</shameless_plug> Come learn about LabVIEW, meet other LAVA members, and share a pitcher of Shiner Bock.

QUOTE(Aristos Queue @ Apr 1 2007, 10:30 AM) This is how I've always done it. Works great. Michael: I'm not sure if I would advocate using LAVA as an general-purpose LabVIEW image repository. I've been noticing, lately, that the LAVA server is not as quick as it used to be.

Cap'n Danger Baby Chute http://forums.lavag.org/index.php?act=attach&type=post&id=5377

QUOTE(keiran @ Mar 30 2007, 04:36 AM) I will do that

Here's an article that I just wrote that might have some information related to your issue: Thinking in G >> Reentrant VI Clone Name Hope you find it useful.

QUOTE(PJM_labview @ Mar 29 2007, 08:14 PM) I don't know how you'd manage to lift the toilet seat up, due to the weight. But then again, the ladies wouldn't have an issue with men leaving the seat up. And, I bet that it would probably be pretty cold against the skin, considering that gold is a great conductor.

QUOTE(tcplomp @ Mar 29 2007, 02:11 PM) Our legal department has advised us not to comment.

QUOTE(Tomi Maila @ Mar 29 2007, 10:42 AM) I am under NDA not to say anything until this Sunday.

QUOTE(karim @ Mar 29 2007, 09:47 AM) I want world peace I need a magic pony

I'm looking to take a business trip to explore the LabVIEW market in Nicaragua (I hear that the surf is also very good there). If anyone would like to set up some meetings in July, please let me know :-) Cheers,

QUOTE(jpdrolet @ Mar 29 2007, 05:37 AM)

I prefer not to use loops, at all -- just use a unowned (floating) feedback node. http://forums.lavag.org/index.php?act=attach&type=post&id=5331 http://forums.lavag.org/index.php?act=attach&type=post&id=5332

QUOTE(Mike Ashe @ Mar 28 2007, 08:54 PM) Hi Mike, Thanks for your support. Yes, submissions are always welcome. So, please feel free to post your ideas and examples -- you might want to put a BSD copyright notice on them, prior to posting them publicly. One of the things on my to-do list is to make it easier for people to participate in the the OpenG process. The first part of the process is really the introduction of an idea for a VI, along with a simple functional specification that includes use cases (examples) for why the VI is useful. Then, the functional spec and use cases are evaluated by the process participants and community to ensure that all of the use cases are valid, a real need for the tool exists, and that the functional spec meets OpenG style guidelines. Then, we move to implementation, which requires a technical spec and a test plan. Finally, once implemented, we must validate that the implementation (including tests) meet the technical spec and OpenG style guidelines. Only then are we ready to release the new VIs. This is why the introduction of new VIs is a little slow. Cheers, -Jim

Hello LAVA'ers, There is a new version (2.6) of the OpenG "Array" library (oglib_array package) available. This library contains several routines manipulating arrays. http://forums.lavag.org/index.php?act=attach&type=post&id=5322 This release... See here for more info.http://forums.lavag.org/index.php?act=attach&type=post&id=5323 http://forums.lavag.org/index.php?act=attach&type=post&id=5324 You can download+install this package using VI Package Manager. Just press the "Check the Network for Available Packages" button to refresh your package list. Thank you,

QUOTE(njkirchner @ Mar 27 2007, 03:37 PM) > The problem with this is you still have a bundle node w/ 25 elements. Not if your events are already in the same cluster. I just wasn't sure if you knew this. I've seen people unbundle events and wire each event, seperately, into the Register for Events node -- so, it's worth mentioning. I'll be writing a blog article about this, soon.

QUOTE(njkirchner @ Mar 27 2007, 02:26 PM) First off, just as an FYI, you can pass a cluster (or clusters of clusters) into the Register for Events node and the events will be available as a nested tree. You don't need to pass each user event reference into the Register for Events node. Second, yes, the dispatch should work fine.

QUOTE(gleichman @ Mar 27 2007, 11:12 AM) I'm not complaining about the order of the symbols. I'm saying that there is a discrepency between the order of the symbols used by the Listbox, Muli-column Listbox, and Tree Control and the order of the symbols in the Listbox Symbol Ring Constant -- this means that if you wire an "unchecked+greyed" constant, your Listbox will display a "checked+greyed" symbol (and vice versa). Also, these last four symbols are new "system checkbox" symbols that were added in LabVIEW 8.0, i believe.

QUOTE(Aristos Queue @ Mar 27 2007, 09:11 AM) I believe that it is because the datalog file refnum is used as the type for GOOP objects (and the datalog file refnum shell has the folded corner, as you mentioned). This choice (to use the datalog file refnum) was made, because (1) the datalog refnum type can be defined by the data type placed inside of it (e.g., making it impossible to wire a Semaphore refnum to a Rendezvous refnum, both of which use datalog file refnums as their reference data type) and (2) because the datalog file refnum's data is a U32 which makes it great for passing any object reference (VI, Queue, repository element index, etc.).

QUOTE(Aristos Queue @ Mar 26 2007, 03:21 PM) My guesses are that its either a confidential feature that you don't want to disclose or its because NI doesn't think that we need by reference objects -- I hope it's the former.