crelf

Thanks for the reminder - there are a couple of stronger beers back home that are often preferred by the ladies. When said beer is purchased by a gent for a lady that he is attempting to pick up, it is often referred to as a glass of root beer (not that I would know - epecially if my lovely wife is reading this... ) I don't think I could drink that much beer!

Not just from us - the people of Dubbo are served by the whole country

Step 1: turn off CAPS LOCK Step 2: RTFM (try a LabVIEW example search for SMTP) Step 3: Rinse and repeat

I don't feel so good... Although I'd thought of doing that, I figured it'd be in bad taste That said, since you went to the trouble, I figured I'd change my avitar to the image you created, but dang it, it don't work: Whew!

Now I'm starting to feel homesick! I can't say I've ever called anyone a "mug galah", but I've certainly called plenty of people "mugs" and "galahs" - both mean pretty much the same thing, and combining them only intensifies the meaning. In fact, that's an ancient aboriginal language technique: if you repeat a word it increases the meaning - for example, "dubbo" means imbicile (that's right Aussie punters - go grab a recent Macquarie Dictonary and look it up!), so "dubbo dubbo" would mean a really stoooopid imbecile. As for the "schooey", it's short for "Schooner" which is the size of beer glass in New South Wales between a half pint and a pint. Depending on what Australian state you're in, beers come in plenty of sizes: middy, seven, schooner, pot, fat, thin... :beer: A fairly accurate reference of a lot of Aussie words can be found on this page on wikipedia. As a country boy myself (I grew up here), I still use many of the terms here in the US (I still can't keep a straight face during the 7th innings stretch at Comerica park when everyone signs that they "root" for the Tigers ). Be warned: some of the terms listed on Wikipedia are regional and/or out of date, so be prepared for flaming (not like Alf on Home and Away: "Flamin' galah!") if you use them incorrectly

Sounds like an excellent idea - and absolutely perfect for an open source LabVIEW toolkit.

Because we can The enum dropped into the datalog file ref gives us a really easy way of creating our own reference types. Why is that important? Each class you create should have a different reference type for a number of reasons, including breaking code when you try to use a method from one class on the reference of another. At the programming level, it separates between classes, which, at the lower level, in essence differentiates between the object repositories. Please have a schooey or two for me (I know you'll comply )

Good luck - vision is a bunch of fun once you get into it. If you need any more help, feel free to ask. PS: welcome to LAVA!

:question: I'm not 100% sure I understand your table - are you saying that the 20003 code in LabVIEW 7.1 was changed to 20012 for LabVIEW 8? I wonder why... Thankfully, the Error Ring only goes up to Error 113

Try this one out - I've used if for a while now. It logs errors form the error cluster to an ASCII file - one line per error with status code and description included. There's also a feature that allows you to limit the size of the error file (making it a FIFO). Download File:post-181-1149805715.vi It also needs this vi to check if an error log already exists (the vi creates one if it doesn't) Download File:post-181-1149805736.vi

You're absolutely right, although I expect that only a few errors may have been added for LabVIEW 8. (as an aside I very much hope and doubt they would have either replaced any of the existing ones or put them out of order, but stranger things have been known to happen ) Well that's pretty disappointing (of course, unless there's a good reason for it to have gone away - anyone from NI want to chime in? Pleeeeeeease??? ) For those of without LabVIEW 7.1, here's an Error Ring Typedef - just put it on your FP and change it to a constant: Download File:post-181-1149805384.ctl

That'd be just down-right distrubing...

Since you're using a webcam (I assume it's USB), you're going to need this too: NI-IMAQ for USB Cameras. Once you've installed it, check out the manual.

Maybe it's because my eyes are glazed over from too much :beer:, but has the Error Ring Constant been removed from the Functions Palette in 8? Anyone know where it is? This was its' location under 7.1.1: ...and here's the same subPallete under 8:

The closest I've ever been to him was in the same country when he was in Melbourne for the opening night of "The Producers" - it's a great show, but I'm still a huge fan of the original 1968 Zero Mostel / Gene Wilder movie. Another great movie of his to watch out for is "The Twelve Chairs" - although there's some of Mel's slpastick schtick in it, it's more of a dark comedy - abosolutely brilliant! Gee, I guess we can consider this topic hijacked... You've all made me see the light - I shouldn't never have abandonded my beloved Mel - he's back now Sorry Kermit...

Vegemite?!? Blaagghh! I can't stand the stuff (where's the :vomit: icon?) No, I've just given Mel a rest - he's been working hard lately. That said, I'm sure I'll miss his attractive mug and he'll be back real soon For those of you scratching your heads, my previous avitar was not a photo of me (I'm much younger than that ), but actually a vintage photo of Mel Brooks, my hero:

Hey Chris - any progress on that CAR? Or better yet - any progress on a bug fix

...and you're probably not going to find it anywhere else either. The super secret private stuff is exactly that :ninja: and whilst it seems to have leaked out, I'm not sure too many people want to break their NI NDAs to go into too much detail. That said, if you're interested in actually using the super secret private stuff to its' full potential, then you might want to check out LAVA's Scripting Forum. Back to the original topic: AFAIK Brain Renken's page is still the authority on undocumented ini settings, although we all need to help him out to add settings when they surface into the general public domain...

Mmmmm - I like my sausages crispy, but not vaporized...

You know, you're right. I've sold my big barbie and bought a wood-fired one instead, which means that I now have a good use for my little chainsaw.

I'd appreciate it if you posted a little example snippet of code so if we're ever searching this forum thread again we can see how you did it.

My first suggestion (as always) is for you to RTFM. You'll find that LabVIEw reserves the ranges of 5000 to 9999 and -5000 to -9999 for custom user error code use, so there's plenty of room there for your error codes. One of the (by far) easiest methods of defining your own error codes is to use the Error Code File Editor (you'll find that under Tools>>Advanced>>Edit Error Codes) - it's an interface that helps you create an *-errors.txt file which is a file that contains all of your custom errors (it's actually a simple XML file). Basically, when an error handler gets and error in, it looks for the error code in your standard LabVIEW error files, then toolkit and add-on error files, and then your custom ones, so you don't really have to do anything special on your BD. :!: dont' forget to include the custom *-errors.txt file in your installer build if you build executables (there's a specific setting for that in the builder).

Check out the new barbeque I bought - it's only a small one on the Aussie barbie scale, but I'll have to make do with it for now...

You'll need to give us more information that "it wont work" - what about it won't work? can you please post the source code so we can try to reproduce your problem?

Thanks Dave & Ben - I feel so young!