crelf

It won't work, or it didn't work? Did you at least try it?

Do a nice icon...

Not that I specifically condone it, but I've seen the same technique with the subVI's icon a representation of the type def itself:

Cluster or subVI? :arrow:

...and your development team members aren't even tempted to look inside.

Your development team sure isn't like mine

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

Oops - the testing I did was under Windows, so that probably won't help you (I get the LAVA list as an RSS feed that only tells me the post titles, and not the category that it is posted in) - sorry about that. I agree with Jim - give NI a shout. Does Karina still work in the Sydney NI office? If so, she'll hunt down the answer for you - and pls say G'Day to her for me...

And this hierarchy is one of the key claims in the original LabVIEW patents (over 10 years later...). So much for the "prior art" portion of patent office due diligence.

I've read a lot of the NI patents[*] with respect to LabVIEW and I don't remember the heirachy being in them. Just about everything else is there including the underlying structure of a VI, dataspaces, icons, connector panes, VI flow diagrams, etc, but not VI heirachy diagrams. That said, it's more than possible that I may have missed that page of that particular patent...

[*] ok, so I'm a geek - but you'd be amazed with what you can learn about LabVIEW's underlying engine by checking them out - I highly recommend it for those who prefer to understand the engine before complaining about it . When you've got a lunch hour to spare and a good cup of tea, here's some of the more interesting ones to check out - I suggest you start form the bottom and go straight to the images section. Of course, some of the patents are more inspired than others

That's a great idea! In fact we're actively doing something similar that at http://www.roborealm.com/ for free!

So where do I plug in my custom LabVIEW components?

Are you using the LabVIEW.ini file for the built app? I'm curious if there's different (or missing) settings between the ini file you're using in your development environment and that of your built application...

I also have been looking for a Mac OS X version

I can't (and won't) speak for NI, but this link might help (it says it's Windows only, but I don't have a Mac to test it on)

I can't speak for the copy that comes with the book, but the absolute best place to download LabVIEW from is the company that created it: National Instruments.

:arrow: Download the latest version here.

The Egyptians did this long before anyone else....

Who can argue with that?!?

Looks like a VI hierarchy to me :-)

Now that's just spooky - maybe NI could use this as an idea for 3D development environment programming?

"...if you're willing to call dataflow diagrams a programming language"?!?!

I haven't had the problem myself, and this might be a stupid idea, but have you tried manually recompiling the VI? Try a shift+ctrl+click the run button - it seems (especially in LabVIEW 8) to have magical fix-it powers

I had both of these, but there was a typo in SuperSecretPrivateSpecialStuff...

Oops

For the lava repository, this is what I got so far...

Looks pretty good to me!

Is there some SuperSecretIniEntry I don't know of yet?

Only these ones.

If you can't find exactly what you need and decide to create this vi yourself check out this link mballa Icon editor

Hey Mark - ever considered putting this up into the LAVA Code respository?

You could use a classic cluster and then make the frame transparent...

I'm looking into a development toolbar

This could be a a good candidate for the LAVA Code Repository...

Since I don't have the data file (you're welcome to upload it too) I can't test the first one, but the second one works fine on my PC

Yeah mate, you gotta brush up your french

P.S. Good luck to the French team... Allez les bleus!!! Allez les bleus!!!

Viva la France! Peuvent ils triomphent contre leurs enimies (puisque l'Australie l

This is a bug that (as far as I remember) will be fixed in the next version of LabVIEW - you need to manually recompile the VI (just hold down ctrl+shft and click the run arrow).

Thank you, that's exactly what I was looking for!

You're welcome!

I have a stict typdef cluster that resizes on the BD, and I don't like it

I'm getting a little confused since you seem to be using the FP and BD descriptors interchangably, but aren't you after a typedef, not a strict typedef?

I can imagine some customers trying to make do with Cubix when the Embedded and maybe an Analog Devices Blackfin was the right way to go.

Just like the folks that try to put together a cRIO system where cFP should have been used

Anyway, as I said "maybe they found an existing COTS system that was comparable"