Jump to content

Stagg54

Members
  • Content Count

    93
  • Joined

  • Last visited

  • Days Won

    2

Stagg54 last won the day on September 28

Stagg54 had the most liked content!

Community Reputation

12

About Stagg54

  • Rank
    Very Active

Profile Information

  • Gender
    Not Telling

LabVIEW Information

  • Version
    LabVIEW 2009
  • Since
    2007

Contact Methods

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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.
  3. As a community member and package consumer I want to support your efforts.
  4. 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
  5. 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).
  6. 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.
  7. 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.
  8. 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.
  9. I was going to ask, but I guess that answers my question.
  10. FYI, the Peter Bokor one crashes a few minutes from the end. The slider says it 1:05, but it crashes around 1:02.
  11. 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.
  12. That is what I typically use... Generally I wrap in a class.
  13. You could call it the jenga or house of cards solution... It works, but if you want to make changes, you better be careful!!
  14. 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.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.