CaseyM

I think yes. If you're architecting code and not aware of OOP principles and LVOOP itself, you're probably hindering your efforts. This is an advanced certification so I think it's fair to require people to know about these ideas. I'd certainly expect someone with a CLA to at least be familiar with LVOOP if I were hiring. The key difference between this and other "advanced" topics is that I see OOP as pretty fundamental to good architectures. Obviously there are places where LVOOP might not be appropriate or even possible, but for a general CLA certification, I think this makes sense. LVOOP is ~15 years old by now so it's not like people haven't had time to learn it like was the case when the CLA certification and LVOOP were both fairly new.

This 100%. I guess we have to all wait and see, but I'm not feeling very good about this for my long-term career aspirations at the moment.

I recently ran into the exact same thing except my offending VIs weren't password protected so this thread definitely helped. Does anyone know what mechanism causes VIs to lose their linking to their lvlib files? I only noticed that it was happening when I came across this error.

You may want to check out this topic as well - some good stuff there.

Cross-posted here: http://forums.ni.com...hread.id=438196 I have an installer for an application I wrote in LabVIEW 8.5.1 that includes nothing but the application itself and theLabVIEW RTE. It used to weigh in at ~75 MB, but since I installedLabVIEW 2009 the installer now takes up ~115 MB. I poked around someand it appears as though some of the extra space is being used toinclude 64-bit compatibility, but is there anything else going onhere? Can I set any options to reduce the size to something closer tothe original or is this something I'm stuck with? Also, in case it wasn't clear, I'm still building the installer using 8.5.1.

Suppose I have two signals - A and B. I want to output signal A followed by some user defined delay and then output signal B on two separate AO channels. This process can be automated to repeat N number of times. Now also suppose that I'm reading an AI channel continuously, but I only want to log data from that analog input when B is being output. How can I trigger logging when B starts? (This needs to be hardware timed so no data is skipped so occurrences and other such software features are out.)

QUOTE (Yair @ Mar 5 2009, 09:02 AM) Good point - I hadn't thought of multiple event structures. I'd be fine with a connector pane style interface as well as pretty much anything would be better than what currently exists.

I'd like to be able to right-click on a terminal, browse over to the "Create" option and have there be an "Event" menu option along with the "Constant", "Control", etc. Bonus points if you could browse to a sub-menu beneath (like with "Property Node") that that had the relevant events associated with that control. Thoughts?

QUOTE (Aristos Queue @ Feb 1 2009, 03:17 PM) I think this needs some modification in order to be correct. Example: Array size = 4 Quotient (after dividing by 2) = 2 Remainder = 0 Median = 2 The indexes of the array would be 0, 1, 2 and 3 and the median index should be 1.5. Using the method above with an array with an odd number of elements produces a median index that is one higher than it should be. The correct algorithm for finding the median index of an array should be subtracting 1 from the array length and then dividing by 2. Example revisited: Array size = 4 Array size - 1 = 3 Quotient (after dividing by 2) = 1.5

I did a quick search and didn't see this before so my apologies if this is a duplicate, but I'd really like it if LabVIEW had the option to have tabbed VIs. I try not to keep too many VIs open at once, but sometimes it happens and it's a pain to Alt+Tab trying to get to the VI you want and don't even get me started about trying to Alt+Tab to another application. Now, I realize that not all FPs and BDs are the same size but I'm picuring something like Excel where all the VIs could be contained in one master window for FPs and one master window for BDs. You could Ctrl+Tab between the different VIs and then you could Alt+Tab between different applications. Or maybe something like PowerPoint where you can preview the FP/BD on the side and when you click on the preview, it'd bring up the FP/BD in the main display area to work on. Again, I think this would be best as an option so that those that work with lower screen resolutions wouldn't be hindered by this feature. What do you guys think?

NO SLuG BacK (following a "Slug Bug!")

Thanks for the replies. I was pretty certain that it wouldn't work. We decided to just to transfer the raw data off the cRIO and to the Matlab processing then. -Casey

Hi all, Is it at all possible to call a Matlab DLL (i.e. MCR) in LabVIEW RT? From what I've seen it doesn't appear so. If, indeed, it is not possible, does anyone have any insights as to how else one might call Matlab code in LabVIEW RT? -Casey

QUOTE (iowa @ Jul 31 2008, 04:19 PM) If you're familiar with TestStand there's a toolkit available on justTESTtoolkits.com: http://www.justtesttoolkits.com/toolkit-details.php?id=167 You can always try requesting a toolkit there as well.

Use the "Set Menu Item Info" VI. It's under Dialog & User Interface --> Menu --> ...