Francois Normandin

I beg to differ. LAVA is a forum for this. As an independant forum, its participants will discuss anything related closely or loosely to LabVIEW. If we have questions about a product, we surely will continue to ask them. Whether or not AddQ wants to continue the discussion is entirely up to you, but deleting parts of discussion leaves a very bad impression and probably will encourage others to continue without you able to correct any misinterpretations. Fleeing the discussion only risks to aggravate it. I adhere strongly to the principles of open source, but never at the expense of stealing intellectual property. Know-how can be duplicated given time and efforts, but copying source code directly without giving proper credits or respecting licensing agreements is a breech that even an open-source fan like myself cannot disregard. Come with a genuine framework completely out of your gut, and the community will give it a chance. Ask for contribution from this open source community and you might even get it. But long time contributors to this forum make a living of creating products as a add-on to LabVIEW. Let's not kill their business to create another one. I salute the effort to build a business out of a completely open source product offering as a marketing strategy to develop your consulting business, but it has to respect the rules and existing competition. Fair competition will benefit everyone in this community. Existing products will need to get better to stay on the edge, new products will attract business and end users like most of us will get increased productivity from a better development environment. If you cannot continue this discussion for legal reasons, please say so. But if you don't want to continue the discussion, I think it leaves a bad aftertaste to all of this, and no chance for redemption.

See the other thread.

Hi Drakones, for simple things like ROI or color threshold, you can venture into doing it with coordinates and events directly on the 2D Picture. But I agree with Antoine that if you need to fit patterns or do particle analysis, it's not worth starting from scratch. Here's a little something to start with. (LV 2009) ROI on 2D Pict.vi

I guess there are some things that "ctrl-U" can't do (yet).

No, just the ones where you'll need to prove you've reached legal drinking age... Don't forget do bring your ID Jon.

I think perhaps you could use the "Qualified Name" property for the library. It seems to do exactly what you need.

A crow? I admit some bars can be scary, but crows? It's way too hot for crows to stick around in August...

Got StreetView? I guess you'll find out in a month or so.

Here.

That's unrelated to NI Week. The stats won't be that specific, but it actually occurs more frequently on 6th street...

I don't want to end up in the picture gallery with you in an ackward posture...

Great, I have a spaghetti spot on last year's t-shirt anyway! (Or is it BBQ rib sauce?) Not that a bunch of programmers would notice on a marron shirt...

Is it possible to filter the twitter feeds for latin characters? If I can believe Google Translate, some of this would be censored anyway if it were in English... (so I won't write it down here)

So cold that you'll see most people wearing pants on a sunny 110F day!

First thing that popped into my head reading this: "I'm Dr.T and I'm a Night-Elf Mohawk." Sorry to be off-topic on an off-topic topic but I couldn't help. BTW, I love this off-topic topic...

There used to be a NI Labs: Neural Nets API, but I can't find it anymore. NI Labs page doesn't mention it and all I can find on Google is an 18-months old discussion forum. I still have the ZIP file on my PC. PM me if you'd like to have it. It's > 5MB, so I'd rather not post it here.

Thanks Justin and to the others who are organizing the BBQ! (By vegetarian food, you mean "beer", right?)

You don't like air conditioning?

Even #12 ? I'd really like that one to be available sooner. I know it would if it were up to you... (Can't vote twice.)

When you close your application, you can use the "Panel Close?" event to ascertain the conditions of closing and decide what are the actions you need to do before closing. When using "Panel Close?", you'll notice that you can choose to discard the event on the right side of your event case. If you choose to discard it, the "Panel Close" event will be filtered out. By doing so, you will handle all the cases required to close your app the way you want and decide which case will effectively stop your loop(s). Or do you really need the Application Close event?