Roland Melkert Wrote:They way Philippe wrote is the intended way of editing shadow files.Thank you both, Philippe and Roland. I misunderstood the warning because I hoped for a separate path of modified shadow files. However, this is not possible, true? So I extract the zip archive before running LDCad and use the 'diff' command later to find my changes I want to send you, Roland, back.
I usually have the official library compressed and the shadow library non compressed during shadow editing. This way you will be sure no official files are save to disk (this will otherwise happen when LDCad e.g. corrected the case of a type 1 line reference).
Roland Melkert Wrote:You info looks ok, I would add a bit more detail though, like so...OK, I study the documentation
Roland Melkert Wrote:HehePhilippe Hurbain Wrote:Great job on connectivity editing! It's a pleasure to be able to define connectivity and test it at once in the same session.Thanks, but I must say it was mostly for my own convenience
I hope we already showed you the opposite is true! This is THE feature, pushing LDCad to completely new level of usability. Really great job!One of this feature effects is that more people can contribute the snap data and (hopefully) save some of your time.
About the repository: good idea! I just, if I can, recommend git even you are familiar to svn so far - with git, you do not need to handle user rights (because we'll not need the write access), merging of branches is no longer a headache and, most important for you: you can see every commit as an e-mail (or "submit request") before you apply it to your tree. What saves a lot of time of the tree maintainer.
Of course, I'll respect any repository format you setup, I just wanted to share some years of experience to help you...