crelf

Okay, so I found it, but it's not in a state I'd be comfortable sharing here (it's got a bunch of our reuse in there that, unless you did the course and got the CD as part of that, I'm not going to share). Anyway, it's pretty easy to re-create. In fact, it's even easier than I mentioned earlier - everything communicates over a common queue: the control and indicator references on the UI VI are sent over to the main VI and then the main VI manipulates their values remotely - so then all the UI VI does is waits to be closed. If that's not clear, let me know and I'll code something up.

You *could* do it that way, but what I think hooovahh is referring to (correct me if I'm wrong hooovahh) is using VI Server to communicate between the FP nodes of a VI that's dedicated to UI interaction and a VI that's acutally doing all the work. All you need in the UI VI is an event loop that has the following responsibilities: send the data from controls that are interacted with to the main VI receive data from the main UI to push to FP indicators that need to be updated (through user events) watch some Boolean somewhere to know when to close (can be acheived with the user events mentioned above) So it's a pretty sparse VI, and can be recreated quickly for differing resolutions. Another huge benefit from using this technique is that you can have different UIs for many different user requirements (not just screen resolutions). If you have an operator UI and an engineer UI then you can switch between them without actually screwing with the underlying main VI that's doing all the work. You can also distribute new UIs without touching the main VI (as long as it's designed well). One application is to distribute new UIs like plugins - very powerful. There was a simple example in the original LabVIEW Advanced Application Development course (the one that VIE wrote) - we had a custom menu for the UI VIs where you could click on a menu and get a submenu showing all the different compatible UI VIs, and you could choose between them dynamically. I'll see if I can dig it up...

Since we're all quoting others: "Stupid is as stupid does." - Forrest Gump's mother. Take from that what you will.

We have a winner

Pfffft. We were named "V I Engineering" before we started using LabVIEW Ugh. I'm working on a project at the moment that has me editing text files on a UUT that's essentially a qnix box. Unfortunately, vi is the only text editor on it

"hard-core" and "hand bell" next to each other in a sentance?!? I used to be a stand-in member of a pealing group in my hometown of Orange, NSW. Guess what the group's name was... I would so pay to see that

I only use the scaling functions in LabVIEW if I absolutely can't get real world signals in. You can (and should) define DAQ channels/tasks/scales/etc in the LabVIEW project - click on your target in the project window and select "New..." - then all of your DAQ settings can stay with your project (btw: I think this is an excellent feature - thanks NI ).

hey Hey HEY! I said drop 2 curl 3, not drop 3 curl 2!

I'll do it for $4* (I'm dure there's a moderator setting here somewhere...) *$4 per reputation point

If you really wanted to put in all that effort, I'd say go for it!

Hey - has anyone heard from hooovahh? He didn't come into work today, and he's not answering his phone...

I was expecting the "Virtual Instrument", and was prepared to subsequently slap whoever suggested that (I'm coming for you Philip Brooks!), but I sure didn't expect some of the other suggestions... Man I love that show! Ha! Actually, our HQ in Michigan is right next to the City of Novi. It's on a trainline from Detroit, and it used to be the 6th stop from grand central, so the platform was labelled "No. VI" - sure enough, it's been known as Novi ever since PS: Novi is pronounced "no-vigh", not "no-vee" as I pronounced it to the cab driver at Detroit International Airport when we arrived here just over four years ago PPS: There's a really good steakhouse in Novi called "The Number Six", although the sign just says "NoVI". I suppose that'd make it the NoVI of Novi... Seriously - if you get a chance - great steaks. Not quite Ruth's Chris, but pretty damn close.

We don't have engineers at V I Engineering, Inc. - we have imagineers Maybe we should rename the company to "V I Imagineering, Inc." Pop quiz: what does the "V" and "I" stand for in "V I Engineering"? (VIE employees are exempt from participating in this quiz).

Sending the reference could give you more control - you could send different references at different times. Also, you might want to manipulate more than the data (properties for example). But I agree with PaulG. - if it's always the same cluster and you only want to work on the data, then just send the data.

...and now I will. Computer.plat-registry.Get Windows Registry Settings_8.5.vi

I could.

A great example of how JKI's unit test framework is excellent for test-driven development - you can compress/group common/like tests. Not appropriate for regulatory industries artifacts under these circumstances, but excellent for on-the-fly testing while you're developing.

Yes - it's a different test case, so I'd make it a different unit test.

Hey you go. It's a little old and I don't gauruntee it works perfectly, but it should point you in the right direction. Computer.plat-registry.Get Windows Registry Settings.vi

Are you writing files directly in the root of the c:\ drive, or are they going into system folders? If it's the latter, the system folders might have different names (eg: local spellings of "Program Files" or "Documents and Settings", etc). In those cases, you're better off getting the location of those folders dynamically either using the registry (good method) or through a sysexec call to "path" (ok method). I've got some VIs around here somewhere that get some local user info from the registry - ping me if you want to take a look at them. On second thought: this assumes that the language of the registry is always the same - is that a safe assumption?

Oo - I like that - that's nice.

FWIW: I'm really enjoying this thread.

Isn't that what you'd expect?

Got VME experience? I need someone for a day or so to consult on a system design (looking for someone to verify/deny that a proposed design makes sense). The ideal consulant would also have some PXI, MXI and VISA knowledge.