crelf

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

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: Your development team sure isn't like mine

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...

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

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 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.

Who can argue with that?!?

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

Oops

Looks pretty good to me!

Only these ones.

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

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

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

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).

You're welcome!

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?

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"