crelf

Right - it's not an image, so the board doesn't recognise it (some boards do this to specifically stop you from linking to their content). The workaround is to post to LAVA first and then post to the NI forums with a link to the LAVA image.

I think we all can relate to this at one time or another during our careers: (from xkcd.com)

"I wire up the wizzle on the wizzles and hit the front bizzle, contrizzles and displizzles on my LabVIEW front pizzle"

What about it didn't work out? Can you share the code that you wrote that doesn't work?

Can you post the two videos for us to look at?

Ahhh yes - the close button I've seen many many less-than-savvy users click that button instead of "save/cancel". Personally, I think that having it there on dialogs like that is unintuative, and there should be an option to remove it. In those cases, I use our own reuse dialog without the close button.

Um, LabVIEW DSC?

Maybe talk to Chris Reed at the Department of Medical Physics at the Royal Perth Hospital (email address in attached article) and/or Medical Connections - they worked on the attached "DICOM For LabVIEW" user solution (which appears in Image Acquisition and Processing with LabVIEW ). DICOM For LabVIEW.pdf

I don't agree with term limits - I think if a representative keeps getting voted in by the people they represent then so be it. I don't think there should be a law stopping the people from electing who they want to represent them, and that's what terms limits does.

What benefits does this have over this: http://lavag.org/topic/11333-labview-tray-launcher ? Can the functionalities be merged?

*sigh* I figured you'd quote that and ignore the rest of the article.

Sorry for the RSS bomb, but there's fresh news on the topic: 'No malpractice' by climate unit

No, you get a handful of functions with the normal LabVIEW install, but the video and OCR functions are in a toolkit called the NI Vision Development Module. Come to think of it, maybe you don't need LabVIEW at all - have you considered NI's Vision Builder AI? It's a more interactive environment that doesn't require LabVIEW programming...

You just listed #1 http://thinkinging.com/2007/06/17/top-5-bad-excuses-for-not-using-source-code-control/

As it should - parents should never be child aware, children should always be parent aware. Hey Jon: can you give us an idea of your application? Maybe we can help with a work around if we know a little more about what you're trying to do.

You'll need to install the OCR toolkit component if you want to use OCR (last I checked it was included in IMAQ Vision?), then you'll need to extract frames (images) that you want (every 1s) out of the video and do the OCR on them individually.

It depends on what you mean by "help documentation" - we use an internal tool (written in LabVIEW of course) that compiles chm file for all our reuse libraries, but we have word templates for user manuals for systems and visio templates for quick reference guides (example below). Quick Reference Guide Example.pdf

Hazzaah! Welcome to the next level of professional software engineering

That's a great saying, but I don't think it's appropriate here. That's like saying you can program most things in a 3GL - people that use 4GLs are weak Besides, my business is test, not reuse, so I'd much prefer to use a tool that helps me with reuse so I can get on with my business.

Mmmm soup... "COTS" is also interchangable with "OTS" <- off the shelf.

Of course you do ...and the "Enterprise" level gives you real control of the administration of your library - read more here: http://jkisoft.com/vipm/ VIE used to make a lot of tools internally (eg: the VISTA suite) because there just weren't any really professional software engineering tools available in the marketplace. Thankfully, with products like VIPM, VI Analyzer, Desktop Execution Trace Toolkit, the Project Explorer, etc, we can limit the number of in-house untilities and rely on COTS products <- someone else designs, develops, maintains (what happens when NI comes out with a new version of LabVIEW that somehow unintentionally blocks the hooks that you were using in your custom tool?), etc, which means we can concentrate more on what we do best: test. I've seen far too many companies get stuck developing internal tools rather than use COTS products to try and save a few bucks (how many of use have tried, and failed, to write our own TestStand-Lite? ) - in summary: in almost every case, going with the COTS product is the smart way to go, and using VIPM for resue is a great example of that.

I've worked at several companies who have tried reuse, and IMHO VIPM is the only solution that has really worked. To apply what I just said in another thread, if you don't use VIPM you'll either abandon your reuse efforts or you'll end up with a BBOM. Now all I want is for someone to come out with TSPM (TestStand Package Manager)

ATES!!! VIE ATES Overview.pdf What you want to do takes some thinking, and there's a lot of little issues that you'll need to address along the way (trust me - if you don't do a deep design phase you'll end up tripping over these little issues, and you'll end up either abandoning the project or with a BBOM ) - and that's why we developerd our internal ATES platform here at V I Engineering, Inc - for projects *exactly* like yours. I'm sorry that I can't really give you any technical under-the-hood details, but I'd be happy to talk to you offline if you're interested in getting us in to help.

kS = kiloSamples