crelf

Mike Holmstrom from NVSI and/or Endevo was writing a TestStand Lite - I tried it out a while ago, and whilst still in its infancy, it had a lto of potential. I wonder what ever happened to that...

Bugger!

Don't worry Dany - I'll step up and accept the award on your behalf :thumbup:

Your code doesn't need to be finished to go into the LAVAcr - infact, code snippets are more than welcome, as long as they're demonstrating something that's useful to the community at large. When you post to the LAVAcr, a new "support" thread is created along with the submission, so users are envouraged to make suggestions, and you, as the submission poster, have the ability to upload new versions as the submission matures.

Well put Todd - I couldn't have said it better myself.

It's not a straight forward question at all - as far as the software component is convered, all you said was "I run the VI". What VI? How does it work? Did you write it? Is it an NI example? Is it an express VI? There are a bunch of ways to acheive what you said you did - and you're assuming that we'll automatically be thinking of your method. Code is worth a thousand words and helps us find errors much much more quickly than text chatting back and forth - it saves your time, and ours. The proof is in the pudding: if you'd posted your code, I'd have worked on it and answered your question by now. Instead, I still don't know what your issue really is.

Right: the scroll bars aren't a property of the subpanel, they're a property of the subVIs that you're loading into the subpanel.

Here's a trick that's garunteed to work or your money back: buy it.

3) You have to share the beer at the Gingerman

SHOW US YOUR CODE! How can you expect us to comment on your process when you're not showing it to us?!?

I knew is was obsolete (the link I posted says so too) - I was just wondering why it was ditched?

Hey Aristos - what ever happened to the LabVIEW Player?

I agree yen - I read the poem this morning, and thought "I've got nothin'".

That was a long time ago - the river's doing much better now.

Happy LAVA-brithday Tomi! That an excellent present you've given youself! You deserve it

How pricey?

Of course

Thanks to everyone who replied: once again, LAVA members have proved themselves to be fountainous resources :thumbup:

The VI Engineering VISTA program has a complexity tool embedded in our project management software, although I'm considering breaking it out and making it available as a separate tool integrated into the LabVIEW project explorer. It uses hueristic measurement of several code facets, including wire counts, nodes, and more. Watch this space for an update coming soon... PS: If you're interested, I may be looking for some beta testers in the near future...

Does not compute!

I feel dirty.

The subVI in the loop is using the buffer allocated by the indicator. It can't use the buffer allocated by the initialize array, as that's required at the input tunnel of the loop.

Holy crap! I concur!

It's all about when the buffer is allocated. In the first example, having an indicator forces a buffer for the data to be allocated (that's the little balck dot on the indicator terminal), and then LabVIEW uses implaceness (ie: just replaces the data instead of creating a new buffer) where it can. In the second example, the little balck dot is on the sub VI in the loop, meaning that every time the loop executes, a buffer is allocated (which is slow - especially when you're doing it 7500 times ).

Nooooooooooooooooooooooooooooooooooooo!!!!!!!!!!!!!!!!!!!!!!!!!!!!