Amaury

I am logging data in binary files by creating typedefs which bundle my relevant data and then writing these straight to binary files. I am running into issues that I can not change my typedefs without breaking all of my log readers. This is mostly inevitable, but there should be some clever ways to encapsulate some meta data in the file and create update mechanisms for older logs. I would like to be able to write a VI that updates from typedef A to its new revision typedef B. The problem is that if typedef A depends on typedef C and tyepdef C get modified, it is not enough so save a copy of typedef A, a copy of typedef C must be made (typedef D) and typedefs A and B must be made to point to D and C respectively in order to be able to have separate typedefs. Perhapse there exists some tool that may help me with the situation. Otherwise, I was going to try and create a typedef database utility. Indexed by type descriptor this database would contain archives of any unique typedef it was ever presented with stored in its entierty (where entirety implies the whole typedef hierachy has been duplicated and saved off). I am looking for a way to programatically save a whole typedef hierarchy with unique names. I hope this makes sense! Thanks

I use SVN for my repository. My repository is set up with a Trunk and Branches. I have been recomending to people that they update their branches each time there is a change to the trunk. What I am finding, however, is that since SVN treets merges as Diffs, if you continualy merge changes in from the trunk into a devbranch as you do developement, and then go to merge changes from the devbranch back to the trunk using a span of revisions which include trunk merges the files which should have been up to date with the trunk apear to be conflicted. Oddly my attempts to study and reproduce the problem don't seem terribly fruitful, as the test cases that I am setting up seem to behave as expected. I'm not sure what I am missing. Is there a way perhapse to use the diff-cmd option in SVN to hook in a smarter differ that can spot the fact that there is not actually a change in a file? Is there somewhere where we can get more advice on SVN with LabVIEW or binary files in general? I may be having more luck as a result of having changed my mime type to "image/x-xbitmap" does this make sense? Should I do this, is there a way i can change the mime type for a whole bunch of files? Any help would be greatly apreciated. Thanks, Amaury