crelf

QUOTE (Graeme @ Sep 29 2008, 03:06 PM) Let us know how it works out for you Gov'ner!

QUOTE (ASTDan @ Sep 29 2008, 03:27 PM) Dr. Teeth for president!

QUOTE (ASTDan @ Sep 29 2008, 11:09 AM) That would work if you didn't want the CVT to grow or contract dynamically (which is, btw, a valid usecase). You're basically defining all the allowable keys up front. QUOTE (ASTDan @ Sep 29 2008, 11:09 AM) Also 2 developers are working on the same program. Developer A addes a variable lets say Sample Rate today. Developer B addes a variable named Sample Time the next day. These are 2 variables that do essentialy the same thing. How do you manage this situation? Two steps: Developer A documents his variable and Developer B talks to Developer A. We also try to define as many of the variables at the SDD stage as possible, then developers become responsible for the group of variables specific to their module and are the person to go to if you want to get a variable or create one. Network the synergies and spread the knowledge!

QUOTE (BobHamburger @ Sep 29 2008, 12:21 AM) Me too - I love that scene. I still laugh so much I snort when Taggert is searching for Heddy's froggy, or when the posse have to go back to get a "shitload of dimes" to get through the toolbooth. It's a wonderful wonderful movie that gets air-time at my family home every Christmas afternoon (imagine: 115 degrees outside, you're overflowing with the feast that was lunch, you're overtired from opening presents at 6am with the kids - and then an afternoon respite with Mel Brooks ) QUOTE (BobHamburger @ Sep 29 2008, 12:21 AM) Your avatar inspired mine, Chris. Now you've inspired me to change mine too

QUOTE (ASTDan @ Sep 29 2008, 10:33 AM) That's a really important point for any loosley-defined datatype. We do two things: Document every key-value pair in the SDD, including where it is spawned and where it is destroyed (if anywhere) We also have a probe VI that watches all messages in the CVT, and can log to disk (this is vital when debugging)

QUOTE (jzoller @ Sep 28 2008, 03:09 PM) http://forums.lavag.org/-t11380.html&view=findpost&p=48336#entry48336' target="_blank">Great minds think alike

QUOTE (BobHamburger @ Sep 28 2008, 08:49 PM) Ahhh the incomperable Tom Lehrer When he's not busy , or , he's ...PS: Bob - it's great to see another Melvin Kaminsky avatar on LAVA Woof!

QUOTE (Ton @ Sep 28 2008, 04:33 AM) Great point Ton - the OpenG Dictionary is an implementation of a Current Value Table (CVT) as discussed above. Don't be confused by it's title of "dictionary" - it's not for spellchecking It's a dictionary in the sense that you can define terms (name/value pairs) and then retrieve (or re-defined) those terms and their definitions (ie: values) later.

QUOTE (Graeme @ Sep 27 2008, 05:43 PM) Are you kidding me? This is a great topic! It's technical, it's talking about a pattern that's a little out-of-the-box, I like it QUOTE (Graeme @ Sep 27 2008, 05:43 PM) ...if you knew of a link to an "LVOOP for dummies" or similar, I would be happy to learn from there. OOP is a pretty important paradigm - have a look at this to get an idea. Whenever I teach an OO class, I show a standard File I/O VI or DAQmx, and ask who has used them - invariably everyone's used at least one of them, and I tell them: "you're already doing OO"... QUOTE (Graeme @ Sep 27 2008, 05:43 PM) Crelf, like OOP, I've seen references to OpenG a lot. ...never having pursued it, though I probably should now... You should indeed. Think of it as LabVIEW with extras - it'll significantly enlarge your palettes, much like other things advertised on the internet... QUOTE (Graeme @ Sep 27 2008, 05:43 PM) ...can I use OpenG VIs at my work place some how? You sure can! Here's a FAQ entry on how to do just that. Anyway, back to the original question: you might want to consider putting together a current value table (CVT) that's based on the attributes of a variant (with polymorphic write and read methods) - you can have a theoretically infinite number of variants (the attirbutes are vairants themselves) that you can name, rather than stuffing everything into one variant. More info here.

QUOTE (Michael_Aivaliotis @ Sep 23 2008, 03:16 PM) Bugger! I missed it

QUOTE (Graeme @ Sep 27 2008, 05:12 AM) You might want to check out the "lvdata" OpenG package - there's a few tools in there that will help you determine and work with vairnat-based datatypes. http://lavag.org/old_files/monthly_09_2008/post-181-1222534330.png' target="_blank">

QUOTE (pdc @ Sep 26 2008, 03:16 PM)

QUOTE (Variant @ Sep 26 2008, 02:27 PM) If you need more than one thing from a palette, pin it, get what you're after, then unpin it.

QUOTE (JFM @ Sep 26 2008, 12:06 PM) You are - history is presevered (although the way Tortoise shows the operation could lead you to thinking it was a delete/add operation).

QUOTE (mballa @ Sep 26 2008, 10:41 AM) That would make a good addition to that OpenG palette... QUOTE (TobyD @ Sep 26 2008, 11:04 AM) That's good to know. It would make a good addition to the VI Description :thumbup: It's open source, so get on over to OpenG.org and make it happen!

QUOTE (LV_FPGA_SE @ Sep 26 2008, 10:23 AM) You just had to ask, didn't you? See the post above yours...

QUOTE (JonMA @ Sep 25 2008, 06:54 PM) :thumbup: Good one Jon - this is one of the OpenG reuse VIs that I use the most: it's in almost every VI that I write that shows it's front panel. I also use the VI that sizes to all objects (with a border of 20 or so pixels) at the end of the VI to show everything again (particularily useful when in development mode). Trick: you can set the border in the size-to-largest-decoration to a negative number (like -1 or -2) as to not see the border of the decoration.

QUOTE (alfa @ Sep 26 2008, 01:30 AM) QUOTE (pdc @ Sep 25 2008, 09:23 AM) Probably that conference only cover the public method. The private method are reserved for the remaining 2%. Congratulations pdc on submitting the 200th post in this thread!

QUOTE (TobyD @ Sep 25 2008, 01:09 PM) I used a third-party serial dll many years ago when there was an issue with the cost of NI-VISA. Back then, if you didn't use an NI serial card, you had to pay a license fee for each installation of NI-VISA (a license would come free with each card). I can't remember how much it was, but it was significant (several hundred dollars), and our client was going to be distributing the software free-of-charge to tens of thousands of their clients, and we only found out about the issue a couple of weeks before launch I created VIs that called the dll that were drop-in replacements for the VISA VIs (well, at least the functionality that we were using) and it worked great. That said, when given the chance, I'd always go with NI-VISA. Also, I don't know whether NI's policy on NI-VISA licenses has changed or not...

QUOTE (alfa @ Sep 25 2008, 07:07 AM) As shown in http://www.imdb.com/title/tt0099582/' rel='nofollow' target="_blank">this documentary.

If you're working on a team that uses SVN for SCC, this is a neat little app written by one of the subversion developers that notifies you when commits are performed in your repository. You can have it watch the while repository, or define areas that you're interested in.

QUOTE (Shaun Hayward @ Sep 25 2008, 10:55 AM) Are you locking the files when you commit? If so, setting local files as read only is desired - and this is fairly common when working with multiple developers (it's not always the case, but I find it comfortable ). If you're working on your own and don't care about the locking paradigm, then you can change it not to lock local files.

QUOTE (normandinf @ Sep 24 2008, 08:41 PM) It's also what Yoopers and Canadians call anyone that live south of the Mackinaw Bridge - hence the beings that live under the bridge Incidentally, Detroit is one of the few places where Canada (the city of Windsor, Ontario) is actually south of the USA, so one might summize that Canadians referring to trolls could actually be referring to their own countrymen...

QUOTE (jones @ Sep 24 2008, 04:49 PM) It depends - what version of LabVIEW was it built in? Also, what do you need? There's no chance that you're going to get VIs with block diagrams, but we might be able to help you get something... Do you have documentation on each of the VIs that you want to get out? eg: what they do, how they work, etc...