Stagg54

As a package creator I would like to be able to see how many people have downloaded my package.

As a package consumer I would like to be able to subscribe to packages so that I get notified when a new version is available.

As a company that uses LabVIEW and has it's own existing internal repository for reuse code, I would like a way for my developers to discover packages in G Central and in our private reuse repository, all from a single portal.

As a community member and package consumer I want to support your efforts.

As some of you may know, we have in the past had an annual CLD Conference in Denver, sponsored by NI. This year it got cancelled and we have been discussing alternatives. After seeing the success of GDevCon, I'm considering bringing something similar to Denver in the next year or so. I'm trying to gauge interest and start some planning. If you could take the time to fill out a short survey, I would greatly appreciate it. https://goo.gl/forms/miafw207AeRAvUxZ2 Sam

Posting your scripting code, so we can exactly what you are trying to do would be helpful. What you are trying to do should be possible. Not sure if there are some limitations way back in 2012. One thing to check would be: Do you save the class before trying to add it to your project? Edited to add: Since the connection between a member vi and a library is a 2 way connection, make sure you save both. I belive a Save All This Library.vi should handle that (it's in the hidden gems pallette if you have it installed, if not its buried somewhere in vi lib).

oh and if your tools need to know what directory things are checked out into, you can always add it to the tools menu. Make them invoke it with the project open and then can pull the items you need out of the project or just use the current project path and compute everything relative to that.

If you do this for external dependencies and everything internal to the project uses a relative path, then your coworkers should be able to check it out to whatever directory they want and not have any issues.

Benoit's suggestion is spot on. That's what I've always done and never had a problem. And you never have to remember to include the vi in your build or mess with any build settings.

I was going to ask, but I guess that answers my question.

FYI, the Peter Bokor one crashes a few minutes from the end. The slider says it 1:05, but it crashes around 1:02.

Thanks Mark!

There is a way to get git to treat specific extensions (and possibly specific files) as binary and not try to merge them... Google the .gitattributes file. It's similar to the .gitignore file and I think it will do what you want.

That is what I typically use... Generally I wrap in a class.

You could call it the jenga or house of cards solution... It works, but if you want to make changes, you better be careful!!

I'm glad that seems to work for you, but... I think you will find the conventional wisdom on version control is that the Golden Rule is "Don't Commit Broken Code". If 1 person checks in broken code, then when everyone else checks it out - if they want to run it, they have to fix what's broken. If 10 different people check it out, then you have 10 different people trying to fix it in 10 different ways and then you have this huge merge problem... Seems like a major headache. If you use a distributed version control system like git or mercurial, you could do local commits of broken code and then only push once it is no longer broken. That way you can save intermediate copies so you can roll back if needed, but no one else is going to check out broken code.

When you are trying to hide something, making it smaller is generally preferable... Making it gigantic almost ensures it will be found...

Just curious how you manage that without committing broken code?

I'm no lawyer, but from the first link: section 0 - 2nd paragraph: "Activities other than copying, distribution and modification are not covered by this License; they are outside its scope." So are you copying, distributing, or modifying SVN? I think likely not. And also the last part of section 2. "In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License." My guess is that IT just wants you to use TSF because it is their standard program that they understand and it's less work for them. This is just a copout for them to justify it.

Also using a turnkey linux virtual machine is simply a super-easy to test out new software packages and play around with them and see if it will meet your needs. Once you figure that out, it's pretty easy to setup a real server somewhere. In the case of the original poster he mentioned wondering if it was the Windows Installer for postgres. Well running it in Linux would help to figure it out pretty quickly. A VM seems to be the quickest and easiest way to do that.

I hardly consider myself part of the "Linux Community". I certainly use it. My answer for any Windows question, starts with why?

You could try running the linux version in a VM.

You shouldn't need to get the key names from the file. It appears you already have them.

I've used Postrgres with ODBC and I've had no issues (other than the 32/64 bit problems that it seems you have already figured out). As far as installation and setting it up, I just download the turnkey linux appliance. It already has everything set up.

I think you are going to find you want a seperate emulated class for each instrument. It really depends on what are doing with the data from each instrument when you get it back. If you are just logging it, then maybe everything is fine with just one emulated class, but if you are making any decisions based on it, then it will probably require a seperate emulator for each instrument. And as for manually entering the response, that works as long as the calling entity isn't going to time out. So you either have to add intelligent code to send back the expected response, or you have disable the timeout in the calling code.