crelf

*exactly*! And then we could talk about how VIPM users can either automatically or manually connect to the repository.

I think the functionality of a package is more important to the framework it plugs in to. That said, I don't mind if extra stuff is shown somewhere that's searchable (like the "Get Info" stuff).

So we're agreed that standardized package filenames aren't necessarily a good idea? I think they are within an organization perhaps, but not in the community at large. I think it'd make more sense to have LAVA packages in a LAVA repository - then "LAVA" or "LabVIEW Advanced Virtual Architects" or "lavag.org" or whatever we want would show up in the repository field.

I think it's even more important to have *categories*, not name standardization. I can image the default view in VIPM getting pretty unruly once a few more packages are released. For example, if I'm looking for some DAQmx stuff and I sort by package name " jgcode_rpk_ni_system_style_daqmx_controls-1.0-1" won't help me.

Yeah, and I'm glad it wasn't implemented - I think the absence of a key is more intuative than a green key.

Congrats mate - well done!

You should still bae able to edit the code (all your DAQmx VIs will be missing, but that's okay) - then when you load your VIs on the windows PC it should find the missing DAQmx VIs again (you'll obviously need to re-save the VIs once they're back on te Windows PC).

"Big" is kiwi for "bug"

Actually, I think it's because you've opened the class outside of the exe context, and it can't find it's parent (or something else?) You're right though, when you run your exe it'll work just fine. I had the issue just recently, although I was loading a lot of related classes from disk (with different relationships), and, sure enough, as long as I did a source distribution of the parent, the icon was there. Either way, it didn't matter.

There's been some discussion over here about finding an appropriate place to distribute templates. Here's a summary: So, jgcode asked the question: what do others do? I wouldn't call that a big, but I'd sure like the ability to have templates in the Tools menu. Maybe make the suggestion on the LabVIEW Idea Excahnge?

There's also this from Matrix Consultants.

My version of the preferences dialog uses the OpenG panel to disk VIs, and they work great. I'll try to post an example tomorrow, if someone reminds me with a PM...

Right - you're trying to read a single Excel cell into a 2 dimensional array - that's not going to work. Also, I'm guessing that there's an error on the error cluster after the convert to variant VI, which might be causing something downstream (prbably the Workbook|Close method) to not execute - that's why Excel isn't closing. I suggest you rearchitect your code a little to use the merge errors VI, instead of chaining all the errors into one wire.

Oh Mike - that is just too funny My first LLOL of the day! I think that's a great idea, aalthough I'd like to see it distibuted as a VIPM package so I can control my project-based configuration management.

Excellent - I look forward to seeing what you come up with

Nope, but you can vote a post up by clicking the green (+) ball on the lower right of the post. LAVA is more of a forum than a collection of Q&A threads, so we didn't think it made sense to allow members to mark posts as specific categories (like "Solved").

Yeah, I don't think this is possible with what's exposed - sorry

Actually, you only need to click once

Is this a deployed application? If so, what were your language settings in the installer?

Are you looking to hire a consultant? If so, check out www.viengineering.com - we have a *lot* of engine and LabVIEW experience.