crelf

QUOTE (James N @ Aug 14 2008, 10:56 AM) Ditto! QUOTE (James N @ Aug 14 2008, 10:56 AM) How do people handle LabVIEW versions in their SCC? I'm primarily talking about the migrating a Reuse Library to newer versions of LabVIEW while minimizing the affect to older LabVIEW code which must be maintained and/or is still being developed. That's an easy one - use VIPM.

QUOTE (jgcode @ Aug 14 2008, 01:29 AM) Yeah - that sounds about right QUOTE (jgcode @ Aug 14 2008, 01:29 AM) ...at the Advanced course last year your old collegue GB took the course. Someone has cut your lunch! It wouldn't be the first time So GB has done the trainer training for the OO course? That surprises me as I thought it had only been offerede here in the US and only in the last few weeks... Actually - I've thought of someone much better to teach the course: Mike Holmstrom! He's Mr. Endevo, he lives in Sydney and is the authour of the Endevo GOOP suite - who better to teach the course?! Oh, and he's a top bloke too... QUOTE (Tom Bress @ Aug 14 2008, 06:45 AM) Yes, we do. I'm not so sure - my company has 2 CPIs (I'm one of them) and we've never been asked to teach any courses. Maybe we've somehow fallen off NI's radar? Maybe the courses that NI offers locally can be covered by local junior FSEs? Maybe NI thinks we're crap? Anyway, I'm not sure that teaching NI courses aligns particularily well with our business model, so there may be agreements in place that are above my paygrade...

QUOTE (jgcode @ Aug 13 2008, 09:57 PM) Specialized courses need to be taught by people that have been trained to teach them (eg: when I took the LabVIEW Advanced Applications course many years ago in Sydney, they flew out a CLA from the US to teach it), so whilst it may not be on the books, if you can get enough folks together then you can get NI to organize a special one for you. If they tell you that it's not financially viable for just one course, you can ask them to combine it with another specialized course. PS: If they need someone to teach it, mention me (your FSE probably already knows me) - I'd be happy to come home to teach for a week EDIT: I just saw that you're in Perth. Well, that's not too close to http://en.wikipedia.org/wiki/Orange,_New_South_Wales' rel='nofollow' target="_blank">my home town, but it's close enough for me

QUOTE (Tom Bress @ Aug 13 2008, 08:45 PM) We do?

QUOTE (Tom Bress @ Aug 13 2008, 04:58 PM) That's a really good point. QUOTE (eaolson @ Aug 13 2008, 05:27 PM) I'm just not quite clear on the difference between edit-merge and check-in/check-out. Could someone explain a bit? It's called the "concurrency model" or "management model" of the SCC system. You can read more about the different paradigms here (there are more than just locking and merging, but they are by far the most common). Summary from that page: File locking: ...lock files so that only one developer at a time has write access to the central "repository" copies of those files. Once one developer "checks out" a file, others can read that file, but no one else is allowed to change that file until that developer "checks in" the updated version (or cancels the checkout). Version merging: ...allow multiple developers to edit the same file at the same time. The first developer to "check in" changes to the central repository always succeeds. The system provides facilities to merge changes into the central repository, so the changes from the first developer are preserved when the other developers check in. Physically merging text-based code is inherently easier than merging LabVIEW code (although excellent tools like LVDiff make it a little easier to manually merge).

QUOTE (TobyD @ Aug 12 2008, 05:08 PM) That's kinda cool, but it doesn't seem to wrok very well - LabVIEW's not the only software that doesn't like the TTF file that you created http://lavag.org/old_files/monthly_08_2008/post-181-1218660322.png' target="_blank">

QUOTE (Yair @ Aug 13 2008, 03:13 PM) Is there any other kind?

:thumbup: Congrats Bryan!

QUOTE (hfettig @ Aug 13 2008, 02:18 PM) :question: Can you have the subVI pause it's caller dynamically? You'd have to make sure that you unpaused it before the subVI finished execution...

QUOTE (Val Brown @ Aug 13 2008, 01:12 AM) Is there any other kind? I'm a big fan of his early work, not so much his later stuff...

QUOTE (eaolson @ Aug 13 2008, 10:50 AM) It's a matter of relativity. Whilst I know that some people taunt alfa in his thread (funny how one poster can personify a thread, and we all know which one we're talking about ) there's a lot of folks in there willing to intelligently argue the sides.

I'm not sure what tags to add to this one...

Hi All, I have a client that has an urgent need for some 778254-01 boards - they're commonly known as "NI PCI 7041/6040E" (the P3 Pentium RT cards that have DAQ included). Does anyone have any spares that they'd be willing to part ways with (I need 6)? If so, please PM me... cheers, crelf [crosspost]

QUOTE (JiMM @ Aug 12 2008, 08:27 PM)

QUOTE (Justin Goeres @ Aug 12 2008, 07:37 PM) I love cats... ...with gravy.

QUOTE (xtaldaz @ Aug 12 2008, 07:26 PM) Except when you were at the bar on Wednesday night

QUOTE (PJM_labview @ Aug 12 2008, 06:12 PM) You need to keep the three colours because the combination of the non-white borders defines the shape of the icon (and hence it's edge transparency). That said, you could offer only one (the highest colour count) and then just copy it to the others in B&W...

QUOTE (Michael_Aivaliotis @ Aug 12 2008, 03:22 PM) Here's my submission - crelf's minifont: http://lavag.org/old_files/monthly_08_2008/post-181-1218570315.png' target="_blank">

QUOTE (Michael_Aivaliotis @ Aug 12 2008, 02:50 PM) True.

QUOTE (Yair @ Aug 12 2008, 02:15 PM)

QUOTE (normandinf @ Aug 12 2008, 11:54 AM) Me too, but whilst I like the whole open source idea, it only works when the project output is useful, robust and appropriately supported. For Subversion and TortoiseSVN, my experience is that's absolutely the case

I think integration into the LabVIEW project is overrated. Our engineers do far more than project-specific work, so the TortoiseSVN client that integrates SCC into Windows Explorer is an absolute God-send for us (we were using VSS previously). I suppose it would be nice to use the project integration, but that would give us more than one place to do the same thing, so it makes it fundamentally less intuative. I know that you can have non-LabVIEW files in the project, but that's not what I'm talking abou there. As for the check-in/check-out vs merge philosophies (a really good point and important for consideration when you're first considering implimenting a SCC schema) - they are very different and equally valid, so it's really a choice depending on your situation. We reviewed both paradigms and chose the former due to several reasons. I'm not saying that that option is inherently better, but it's more appropriate for our situation.

QUOTE (Ton @ Aug 12 2008, 12:27 AM) No problem - I had the choice of either putting it here or removing it from the queue entirely so the choice was obvious...

QUOTE (Tom Bress @ Aug 12 2008, 09:34 AM) We use Subversion + TortoiseSVN across our whole company (not just for software SCC) and are very happy with it.

QUOTE (JiMM @ Aug 12 2008, 08:30 AM) My work here is done