Leaderboard

Excercising the Identity principle and doing some substitutions means That would mean that "You wish that you were alright." Ben

I can't argue with that The RSS feed means I'm always connected

I realize this is a very old post, but are you aware of the optional Convert State for Save ability? I recently needed it, so I stumbled across this post in my search for it. Convert State for Save stuffs the State Data into a Variant indicator that gets embedded into the caller VI's data when the caller leaves memory. You handle the Variant in the Init ability by populating the state according to which elements of the state you stuffed into the variant. I could only find good information on this in the Advanced Architectures in LabVIEW course by VITech. Sorry, I need to see what's one better than "One Hit Wonder!" FAIL!

Touche! But I don't think that works. The substitution is only valid if the set of people who are alright is equal to the set of people who are from Australia. JG's comment doesn't say 'Australians are the only people who are alright.' It says, 'people from Australia are alright,' implying Australians are a fully contained subset of all the people who are alright. According the premise, it's possible to be alright and not be Australian. But that doesn't satisfy my wish. My wish is to be Australian. Being alright is just a fortunate side effect of being Australian.

I've been using Mercurial with TortoiseHG and Kiln (Kiln is free for two developers) since this last summer and I love it! It sometimes surprises me how easy some activities are compared to how I used to have to do them with VSS / Perforce / Surround SCM / DesignSync (don't ask about that one... ). It is really easy to manage when I am the only developer, but also isn't too bad in a multi-developer environment either. The ability to go back to a tagged release, make a small change, perform a build and release (and tag), and then merge that change to the mainline is so easy in mercurial and next to impossible in the other environments I have used. It has literally saved me days of work because of how easy it is to manage releases, bug fixes, major changes with the branching and merging features. I have a major project where another developer is making sweeping changes that are not all backward compatible yet, but we are working from the same repository and I can still perform stable maintence releases. Meanwhile I have another branch where I am gutting the entire structure of the program. The merging is a little lacking, but I am working on a simple tool to allow multi-file merges with TortoiseHG (LVMerge ends execution before the merge is actually complete and you miss the next file merge). A diff tool also needs a little work to support to diff changesets when multiple related files are different. Unfortunately LabVIEW's compile at edit time and sub vi dependency means that if multiple related files are different then the single file diff won't be entirely accurate. The only way I see is to use the Mercurial commands directly to "update" to each of the changesets being compared in their entirety and then compare them in different directly structures. Merging doesn't seem to have this issue. I was thinking a hierarchy ordering of the vi's to merge might be necessary in order to get it correct, but LVMerge (at least in 2010) is very good. Now I just need to trick out the interface to "wait" until the merging is finished, cancelled, or errors out. Right now I just have a "next" button. Is anyone else working on an implementation of the "LVMerge" for mercurial that supports multi-file merging? As far as an API for the project I don't really see a need except for maybe a hotkey shortcut to commit. One of the main reasons I think it is easier is that you don't have to "check in" and "check out" every file individually. I just make my updates for a certain feature or bug, then commit all files from explorer. When updating to different changesets you do have to revert all your files manually (I usually have everything closed when performing updates). On a final note...no annoying "status" files in my working directory!

I'm not sure if you talking about LAVA and/or other fourm(s), but rest assured that we try really hard to leave threads alone, especially those in the LAVA Lounge, where just about anything goes. There have been occasional moderator interventions, but they usually only come when a member contacts us and asks us to do so - and even then we make a judgement call on whether to step in or not. Even then we usually ask everyone on the thread to cool down for a while. It's very rare for us to lock a thread, and almost unheard of for us to delete a thread (unless it's spam, for example). If you think a post or thread of yours has been unfaily handled, please let us know - anything we delete remains in the moderator trash can for a period of time, and we'll review it for un-deletion. We're a group of people, so we might make a call that's wrong, and we're always open to taking a second look. That's the spirit! Right - except that it's difficult to articulate a truth with with our inefficient communcation abilities, and even more difficult to perceive one communicated to us. In short, we spin, based on our own experiences, environment, and perceptions of those we're conveying to/from.