crelf

Bonjour mseb - and welcome! (I'm actually off to France in a week - a few days in Paris and a few more in Toulouse, so I'm practising my very very poor French - merde!) You'll find us a pretty relaxed bunch, although passionate when it comes to certain things. I'm sure you'll get a lot out of LAVA, and we hope to get a lot from you too

IMHO: the first thing you might try is getting a new avatar - this is a respectable engineering forum, not a college student hangout. As for your TestStand issue, what you're looking for can't be done with the simple OI, you need to take a look at how the "Full Featured" version does it when handling menu events.

RDA? Now there's something I haven't heard of in a long time! I don't think NI-VISA is what youre looking for - perhaps writing a local app that acquires the data and publishes it to a Network Shared Variable, and then accessing it remotely is the way to go (since, it seems, NI is winding down DataSocket) - you could have two way communcation fairly easily, so the remote app can set the acquisition settings and the local one can stream the data back...

You've listed a bunch of inmprovements that you're not interested in, but they're still improvements. And what about the ones you didn't mention: the fantastic new project explorer, better SCC integration, multiple target building, separated project instances, and autosave capability, OO in the core, etc, etc, etc... You say that the 5 -> 6 and 6 -> 7 upgrades were more significant than the 7 -> 8(.20) upgrades?!? I couldn't disagree more! :thumbdown:

yeah - that funkyerrorclusterwirecolor thing has been around for a while - initially I resisted it as I thought of the error cluster as just another sort or cluster, but I think I'm starting to come around...

Nicely summarized

I can understand that using transparent anything on a BD could be considered as poor programming (in fact, the NI VI Analyzer gets upset when you put anything in front anything else). Still, I'd like to be able to set my free labels to default to anything - maybe a colour box somewhere in the settings dialog in future?

I know I'm chiming in late on this, but I can't agree more - I could sooooooooooo use something like this! I can't count how many times I've seen LabVIEW developers create their own "TestStand Lite" to do simple sequencing, only to fall on their faces when they need to do anything remotely complex or really reusable. I think that a real NI-produced "TestStand Lite" would be an excellent conduit to get current LabVIEW programmers into TestStand! :thumbup: Anyone from NI like to comment? Pleeeeeeeeeeeeeeease?!?

A quick (pun intended) thank you to the NI R&D team for dramatically decreasing the LabVIEW 8.2 star time - great work! :thumbup:

I'm sure you'll be able to make something up intelligent-sounding Other than dabbling in scripting, I don't think this can be done... I was hoping that grouping can be used as a work-around, but wires can't be grouped to other objects...

Perhaps a candidate for the LAVA Code Respository?

Confirmed.

<insert Gregorian chant here>

Maybe you could convert your data to a variant and add the "name" as an attribute?

I'm not sure I understand, but are you just looking for some way to name elements in a cluster so they can be unbundled by name? If so, try "Bundle by name" with an input cluster that defines the names:

Well said!

Oh - and don't post the same thing twice in different places - it's annoying.

*sigh* RTFM!!!! Take the paintbrush tool, select white and click a clear area on the the FP

Use the paintbrush tool - select white and click on the graph background. You can also set the colours of a bunch of stuff this way - the traces, grid lines, etc.

Brilliant! I don't know what you're talking about!

- make sure you watch all the links on the right side - there's heaps of them!

Crazy is what it is - just crazy. As a (retired) parachutist, I wouldn't try anything like this under chute - maybe in freefall, but then it wouldn't look anywhere near as effective.

Bugger I don't think that can be stressed enough, so let me reiterate Jim: THERE IS A TIME AND A PLACE FOR OOP. OOP is a tool, and just like how you can drive nails with the end of a wrench, a hammer is a much better idea. A word from the wise: please don't overuse OO - if you are considering using it, make sure you take the time to plan the architecture first, and then take the time to confirm it's still the most appropriate model.

Pitty I can't select more than one option...

But you can't have more than one duplicate - as soon as a duplicate occurs, it will be detected and the arrays values will be set back to what they were before the duplicate existed.