crelf

OK - I've uploaded the presentation video in the first post in this thread here. I didn't screencapture the examples, but you should be able to see what I was talking about from the video and the code that's included. Thanks Yair - I'll try out Mediafire and see how it goes...

We're getting totally off topic here, but what would happen if the property node did ignore errors? Would the error output be the error input? Would errors that occured in the property node be merged? Wuold this be extended to VIs and primatives (and other things too)? Of so, how would they be handled? I agree that it *could* be useful, but I think what we have is intuative and works fine.

That's actually pretty good, although it lead me to this:

I'm not short - I'm vertically challenged.

Yes, that's exactly what I mean

I agree that's a valid conern - and it certainly should be considered for every feature addition/change/deletion, but IMHO I don't think it's a strong enough reason to not introduce new functionality. If that was NI's policy, I don't think we'd have any features like LVOOP.

Update: idea added to the NI Idea Exchange here.

Me either I still have old old old version 6 (which has poor alpha channel support, but still does most of what I want when I'm doing something quickly).

I totally *don't* want that - that'd obsfucate to much IMHO. Use the "Clear Errors" vilib vi. I think that, rather than adding this functionality specifically to the property node node, I'd rather see the exection sequence container we talked about here. ...and that's totally valid if exectution order is important for that part of your code and it can't be controlled otherwise.

I use Paint Shop Pro (not free), but a lot of people like GIMP (although I found it a little difficult to get used to). I occasionally use Adobe Photoshop and Illustrator when I'm doing serious artwork (for print publications for example).

I always figured that you should use locals over property nodes (for reasons already mentioned) - unless you were already using a property node anyway (to set some other property). Also, when speed really isn't an issue, I like that I can use the error clusters of the proprty nodes to both force execution order and decisions based on those errors (note: you can right click on a property node and select "ignore errors inside this node" or something like that).

youTube only allows "general" videos of 10 minutes - the talk is more than 55 mins Before anyone else says it: prepare to be disappointed. I'm a slightly overweight bearded man in his mid thirties. Well, at least my wife liles the way I look - sometimes I wonder what's wrong with her, but never enough to actually ask her... Actually, you can see a photo of me on my LAVA profile page.

OK, I've rendered a video of the presentation - does anyone know of a good place to upload it to? I'd prefer not to clog the LAVA server - I'd rather upload it to somewhere else and link to it from there.

Ha! Hopefully that's not duct tape - it's speed tape (sometimes known as 600mph tape).

Thread moved. Remember: if you want a moderator to do something, never write it in the thread - we might miss it: always use the "Report to Moderator" button.

You know what, I don't think we have... Who wants to go first?

"Stop being such a jerk, Alexandar"

I don't get it... ...often

I wholeheartedly agree. The GDS adds several fucntions that really compliment OO in LabVIEW (like the UML tools, as well as more simple stuff like the clone class/method features) - even if you're only working with the native LVOOP, then it's definately worth installing the free community edition.

If you really care about the quality of LabVIEW, be proactive and sign up for the beta program. I do it because I'm selfish: I want the features that *I use* to be good, and being part of the beta program ensures that. Can you post an example that shows the issue that you're having?

I waited 15 minutes to respond because I was so annoyed by the very ignorance and arrogance of that statement. Now that I've settled down a bit I have come to think that there is no value in responding to it directly. To respond in a more general way: Detroit has a bad rap, and that's mostly because of the unfairly-lingering reputation of the 60s and 70s, as well as the media's "infotainment" approach to selling their news as a commodity. There are bad parts of every city in the world. People get mugged in every city in the world. Layoffs are happening in every city of the world. Frankly, if you base your image of Detroit on such ignorance, then I don't want you here - you're bringing the place down. As a good friend of mine once said: "If you don't like the place, then either do something about it or leave. By leaving, you're improving the place, and therefore are doing something about it." PS: as a premium member, my posts bypass the profanity filter. It took a lot of restraint to not demostrate that. PPS: I love this photo on the CBCNews.ca website:

I'd address your copyright questions to copyrightagent@ni.com

The dust came from out west - chech this video out taken in Broken Hill, NSW: http://www.abc.net.au/local/videos/2009/09/22/2693489.htm?site=brokenhill I remember the occasional dust storm as a kid (I grew up here) - one of the major issues was that all the top soil would get picked up so there was nothing for the farmers to plant their crops in

Bring it on! Welcome to the community