crelf

Actually, my current environment spells it: "3.28084 feet"

You might want to hang on for a little while for the next version to come - I assume that it'll be pretty soon...

Gee that was quick Welcome John!

Hey Daryl - welcome!

To me, an ###### is a type of animal. It looks like the LAVA swear filter doesn't recognise "arse" - let's find out: pain-in-the-arse arse scratcher arsehole Nope - looks good to me

Errrr - isn't that the way everyone says it? Or is the other way just an Americanised thing? I'm not so sure that the phonetic pronnunciation changes because of time, but more due to geographic location (which then, in turn, bastardises other regions) - as a physicist, I like a metre to be a metre, irrespective of its' geographic location nor its' existance in time, so I'd prefer the dictionary to be a standard (there should only be one dictionary - there's only one English, right? )

You're, like, totally welcome dude - furshure!

Of the top of my head, you could use reflective memory - write your data to a rm device, and have your host (Windows) read from it and save it. You would have to write some sort of handshaking so unsaved data isn't overwritten, but that wouldn't be difficult. NI has rm VIs that are very basic, but sure do the trick (we used rm on a porject that had 4 RT controllers + 1 Windows controller).

Wouldn't a true anarchist spell it incorrectly anyway?

This one.

I don't think it would kill NI, but (and this is just my musing - I have no real data here) I think that early August might be the cheapest week in the year to hire the Austin convention centre... If they changed the timing, that might result in higher conference registration fees and other associated costs, so it might actually make it less viable for people to attend. Amen to that!

Completely - I was the same, until I studied under Mikael H. from Endevo - then, suddenly, one day:

A big congrats to Mike on making it to post 500 - very cool! :thumbup: We all learn a lot from you, and are glad you're here! PS: don't forget to <customise this text>

Actually, it's just a figure of speech that is usually followed by intense laughing, back slapping, and another round of beers. The only time it is socially accpetable to drink water is when you're brushing your teeth, and some of the water mixed with toothpaste is accidentally swallowed. This is to be followed immediately by gargling a beer (and swallowing the result, of course). Disclaimer: I don't want to make myself out to be a huge beer drinker, as I know that doing so will come back and bight me on the arse during NI-Week... - hey, that kind of looks just like a map of Australia!

Awesome - thanks so much for the update (oh, and for the highly unambiguos hint as well )

Odd indeed. The secret of designing an appropriate architecture is to know the possibilities intimately, and then be able to make an unbiased decision on which one(s) to use, and in what combination(s). I have know several LabVIEW developers who insist that OO is useless, and others that insist that all projects should be done in OO - frankly, IMHO, that's both shortsighted and ignorant. As always - pick the right tool for the job. Just because you really like your new screwdriver doesn't mean you should use it to drive nails. It's also a great benefit to have knowledgable people around you that can give you their :2cents: on the pros & cons for each architectural paradigm in each specific situation...

It's supported, but most often not a good idea. One of my colleagues used a nested event structure to conditionally determine if a user had mouse-downed on an image indicator, and then track the mouse position - it worked realtively well once all the appropriate precautions were taken into account (eg: should you lock the UI during the operation of the outer or inner event structures? Can you know with absolute certainty which event structure will grab and event? Can you use dynamic registration of events instead? etc). All that aside, I've got to agree with didierj - it doesn't sound like you need to nest event structures at all.

Nice - very nice. We have a proprietary test executive that uses sub-panels to dynamically show each test step's UI (you can make a step open it's FP if you like, or you can just follow a standard design and have it show up in the test executor's UI) - it works just fine:

Why must you all mock me so?

The OpenG Commander installer uses a wizard-like interface, although it doesn't use subpanels (it is compatible with LabVIEW 6.1 - before subpanels were invented )

The size of the project is irrelevant - it's whether you can disseminate objects in it's architectural design, and whether thoose objects need to be scalable - whether you need the ability to instantiate them. Size doesn't matter - at least that's what my wife tells me...

Disco baby - yeah! With that hair do, you look like Lady Tottington from Wallace & Gromit: The Curse of the Were-Rabbit!

. . . You can always tell when an Aussie is really really upset - he goes very very quiet...