crelf

QUOTE(Norm Kirchner @ Nov 7 2007, 08:32 AM) Is there a reason that your other programs are blurred-out? Who are you trying to protect? :ninja:

QUOTE(Michael_Aivaliotis @ Nov 7 2007, 06:28 AM) :thumbup: ...and I sure hope that this time of enlightenment is imminent!

QUOTE(MikaelH @ Nov 6 2007, 06:35 AM) Right - that's what tcplomp suggested above. QUOTE(Justin Goeres @ Nov 6 2007, 06:38 AM) Just to be completely pedantic about it... We've come to expect nothing less

QUOTE(jpdrolet @ Nov 6 2007, 12:25 AM) This all confirms that there is no generic method to detect if an input is wired. What you're suggesting is a hack that just checks if a number is valid for a particular instance (you might as well just use In Range and Coerce). Sure, it's a work around, but I'd need to be pretty desparate to label such a sub VI as "Is Input Wired?" QUOTE(adriaanrijllart @ Nov 6 2007, 04:25 AM) I also like the suggestion with two different vi's: one required inputs, the other not. The programmer should know what he is doing. You probably want to wrap the two of them in a polymorphic VI so it's easy (and obvious) to switch between them, just as Aristos suggested.

QUOTE(Cambio @ Nov 6 2007, 03:52 AM) Can you please upload a couple of examples of what you've tried so we can have something to start with? They don't have to be full working apps, in fact it's better if you mock-up a couple of quick examples that are only appropriate to the functionality that you're after.

QUOTE(Gary Rubin @ Nov 6 2007, 04:04 AM) Yep - Michael removed it late last week in an effort to speed up page loading. Personally, I think it worked...

QUOTE(neB @ Nov 6 2007, 02:07 AM) At least you're honest Maybe you should have posted a few days ago to coincide with Hallowe'en? QUOTE(Congress mandated Public Law 106-398, Section 220) It shall be a goal of the Armed Forces to achieve the fielding of unmanned, remotely controlled technology such that… by 2015, one-third of the operational ground combat vehicles are unmanned. That's a pretty audacious goal...

QUOTE(Zeclark @ Nov 5 2007, 06:31 AM) Have you tried something like \\192.168.1.128\484833\productXX.jpg as the path? I don't know anything about the smartcam that you're using, but can you share the directory that the files are in and then just map the directory as a drive?

QUOTE(Norm Kirchner @ Nov 5 2007, 04:03 PM) "Vootshtaps! Vootshtaps!" That'd be most excellent! Souds like the LAVA user group has a new agenda...

QUOTE(Norm Kirchner @ Nov 1 2007, 03:53 AM) If you're blue and you don't know where to go to, why don't you go where fashion sits?

QUOTE(Aristos Queue @ Nov 5 2007, 07:03 AM) Thank you Aristos, for putting eloquently what I was struggling with to verbalise. :thumbup:

QUOTE(hviewlabs @ Nov 5 2007, 04:28 AM) Awesome! Sign me up! PS: http://419eater.com/' target="_blank">take a look at this - there's a bunch of stories there on scambaiters (warning: there's a lot to read, and you'll get sucked in )

QUOTE(LV Punk @ Nov 2 2007, 08:47 PM) Just what are you trying to say ?!? PS: you're all officially geeks with far too much time on your hands!

QUOTE(robijn @ Nov 2 2007, 07:44 PM) Time for another plug Whilst node count is interesting, some of them can get in the way of an accurate relative determination of code "size" (more informaiton here). Sounds like you'd be interested in the VIE LabVIEW Metrics Tool - it more accurately measures the "size" of your code in a varibale that we call "GOBs" ("GObjects - can't tell you too much as the forumla is proprietary, but let's just say that it's comparable to Logical SLOC) and the complexity (exactly what you've asked for in #3). You can download the tool for a free trial here (it's part of the VISTA Metrics 1.2.0 Package).

QUOTE(nabhi @ Nov 1 2007, 07:16 PM) Yep, I've used a bunch of SBCs in the past - as far as LabVIEW's concerned, they're standard PCs, so they work great.

QUOTE(Michael_Aivaliotis @ Nov 2 2007, 01:18 AM) Heeey! It seems a lot faster now! Thanks Mike! :thumbup:

QUOTE(sprezzaturon @ Nov 2 2007, 12:22 AM) I think it's more akin to buying a DVD player that plays DVDs fine, but not your DivX-compressed DVD-Rs. You can apply a firmware update, but it's gonna cost you QUOTE(Neville D @ Nov 3 2007, 07:22 AM) What kind of Developer Suite do you have?? If you got all those disks, then you would seem to have a full Vision Suite. That's a really good point - if you have the CD-ROMs, then you probably have the license too. Open the NI License Manager and select the porduct that you're interested in, and then activate it with the license key that came with LabVIEW - that'll tell you pretty damn quickly on whether you have a license or not...QUOTE(siva @ Nov 2 2007, 08:32 PM) may be you could edit the Source code and recompile it to gid rid of that message box.. Go to the naughty step!

QUOTE(LV Punk @ Nov 2 2007, 09:29 PM) Thank you In fact, if you use it in conjunction with our metrics tools, it's a good way to measure the progression of a project.QUOTE(LV Punk @ Nov 2 2007, 09:29 PM) ...I blurted out "I thought everyone at NI was on the LabVIEW team!" It was probably bad form on my part to say such a thing, and Brian seemed a bit uncomfortable with my comment. Brian's got a pretty great sense of humour, so I wouldn't be too worried about stepping on his toes. He was probably unfomfortable because he had a great comeback that may have been politically innappropriate QUOTE(tcplomp @ Nov 3 2007, 01:41 AM) OK I downloaded your total shameless plug, but I get a not-registered error when running the app, is there something I have to do? If you filled out the webform correctly, you should be receiving a key shortly.

Frederic: Werewolf! Igor: Therewolf!

QUOTE(AnalogKid2DigitalMan @ Nov 1 2007, 06:47 AM) Sorry - I should have mentioned - the VIE LabVIEW HTML Documentation Tool is part of the VISTA Code Reuse Solution Package - you get a couple of extra tools as a bonus QUOTE(AnalogKid2DigitalMan @ Nov 1 2007, 06:47 AM) If anyone asks, T&A Engineer is Test and Automation Sure it does Not that there's anything wrong with that...

The VIE LabVIEW HTML Help Generator is a tool that compiles fully searchable, indexed and linked chm (they're the same type as standard Windows help files) and html reports from your code. It compiles documentation from your VIs, front panel nodes, block diagrams, heirachy, etc and bundles it up into a neat and traceable package - perfect to deliver to your customer and great to include with your project in your SCC system (ever been asked to re-open a project that you haven't worked on for a while? The VIE LabVIEW HTML Help Generator will save you buckets of time in coming back up to speed on it!) I'm no snake-oil salesman, but I don't expect you to take it from me! Here's an example: everyone knows about the LabVIEW Config File VIs in vi.llb: Here's a compiled html file created by the VIE LabVIEW HTML Help Generator for some of the most often used LabVIEW Config File VIs: Download File:post-181-1193851655.zip So what are you waiting for? It slices, it dices, it julianes, and you can put it straight into your dishwasher!* :!: If you'd like to get your hands on a free trial, click here. (Actually, I'm not in Sales or Marketing - this is just a shout-out to let you know about a tool that I couldn't live without ) * Product does not slice, dice nor juilane. Do not place your computer in the dishwasher.

QUOTE(LV Punk @ Oct 31 2007, 08:27 PM) "What Knockers!" (that's one of my favourite Mel Brooks movies, but what can I say? They're all good!)

QUOTE(zappa2 @ Oct 31 2007, 09:24 PM) The Hytek Automation toolkit is pretty damn comrephensive for $399. If all you want to do is acquire and display, I agree that NI-IMAQ for USB Cameras is the way to go, or you might want to try Pete Perente's drivers - they're old and unsupported, but might do what you want with a bit of twiddling.

QUOTE(JDave @ Oct 31 2007, 04:31 AM) Yes and yes Using connector panes is a useful way to make sure that LabVIEW only opens appropriate VIs - when you open a reference to a VI using a static VI Server open, it will error if the connector pane of the VI is of the wrong type. Using naming conventions means it's easy for humans to differentiate between plugins and non-plugins. That said, I usually distribute plugins in their own folders and have the calling architecture traverse it's plugin directory and one level down - I just find uninstallation cleaner this way. QUOTE(JDave @ Oct 31 2007, 04:31 AM) If you use an llb file there is the option to specify a 'top-level VI'. I'm firmly in the camp of "llbs should never be used". They are a relic of when OSes were limited to 8.3 naming conventions. They're difficult to control under SCC. If you want to encapsulate your code components in one file, use something like a zip file instead. At least if it's corrupted, there's more wide-spread usage, hence more support of getting to your files (but they're already in SCC, right? )

QUOTE(silmaril @ Oct 30 2007, 08:30 PM) :thumbup: Awesome!