crelf

Two excellent ideas, but I think they're out of the scope of the idea I'm suggesting. That said, I think what you're saying is important, so I've created Allow copying of FP and BD elements from locked VIs (that one really irks me too) and Allow "Find All Instances" on a locked VI.

You're almost there - the "IMAQ AVI Get Filter Names" that you've disabled will list all the compression technologies available to you - pick one of these and give it another go.

You need to set the following to TRUE: LabVIEW Options > Environment > Saving VIs > Treat read-only VIs as locked LabVIEW Options > Environment > Saving VIs > Treat read-only VIs as locked > Do not save automatic changes Once you've done that, support this.

I've added a "Getting Started Window" category to the LabVIEW wiki so we can expose all of the ini settings: http://labviewwiki.org/LabVIEW_configuration_file Please add any that you know of.

(Continuing the Cross Posting) Forget I mentioned SCC, as this really isn't a SCC issue. In general, ask yourself this question: should you be able to edit a read only file without explicitly setting it to edit mode? I think the answer is no.

I posted an idea over on the LabVIEW Idea Exchange titled "Set "tread read-only VIs as locked" to true as default" - reminding us not to edit a VI if it's read-only (you can, of course, still change to edit mode with a ctrl+m, but that's explicit). This is especially important when using the needs-lock property with non-integrated SCC products (like SVN). This also discourages the bad habit of only getting an SCC lock on a file when you're done editing and are saving it (I've seen ppl do this from the "Save" dialog ). I'd appreciate a few extra votes over there.

You can recert for free at the summit. Hmmm - good question. I guess I see the CLA summit + NI-Week = rounded NI experience. NI-Week is when we get to learn about all the cool stuff across the complete NI range, the CLA summit is a deep-dive that's actually about architectural concepts (go figure). So, if I had to put a dollar value on it, I'd make it the same as the cost to attend NI-Week.

Another option is a current value table (also known as a currnet value repository) using variant attributes (discussed a little here). We have an internal reuse library that wraps the get/set methods (think polymorphic) and includes other functions like write-to/read-from file, search for tags using wildcards, probes, etc. There's also a CVT example from NI here - it's strictly-typed, but it might give you some ideas.

FYI: The beta download is now available.

I do?!? So everybody wins!

So I finally isgned up for a DropBox account - I don't know how I ever survived without it!

Try making the tab autosize, then draw a box completely around the locked item (don't try to just click on it) - that should select it.

Right - now that you've posted the verbiage, I agree with AQ. You can link all you want, but you can't link and use the text "National Instruments" (or any other NI trademark) for the link. NI owns the "National Instruments" text in this context, and is totally within their rights to control its use.

I think the "cr" in your examples probably mean carriage return, not actually the c and r characters, right?

An excellent topic! Well, you *can*, but it's a little unintuative. You can create a class that exists in the parent project, and then manually copy it to a new location to create a new instance (like a template, if you will). Then load your plugins dynamically by filepath. The trick is that when you deploy the new plugin, you'll need to build a source distribution first, then an installer, which means that some files of the parent installation will be overwritten, but as they're the same file, it's okay. I think the approach above is fine. We have a couple of projects that have parent and child classes (ie: plugins) exist completely separately and (once we worked out the difficulties of distribution) it works great. This is what I'm talking about: