> > Philip wrote: > > > > First I did as I have done in the past. "Edit>Save > > Technology". But when I use the popup and pick "gear_dsp", > > the filename either blank or jibberish and when I write it, it > > puts it in my current directory - NOT the directory containing > > the original technology file.
> Tim wrote: > > The fix I made a couple of days ago should have taken care of > paragraph (1)---no more gibberish. It will instead give you the > filename of the "gear_dsp" tech file. It did. I made the change to the source file, recompiled, and it's happy now! > The fix I just pushed to the git database will now prevent you > from writing back the several objects you imported from the tech > file back to the same techfile, overwriting the original contents. > Instead it will say "Attempt to write a truncated technology > file". Sweet! > I thought about writing a routine that would actually merge the > new object back into the existing tech file, but it was looking > like a lot of coding work for a feature that can be handled in > other ways. The warning should be fine for me. It's forgetfulness I'm most worried about causing data loss, so just having it yell at me that I'm doing something stupid _should_ be enough to stop me. *smiles* > From earlier in your email: > > > My new object (solus8) is similar to an existing object > > (solus16), so I loaded solus16 from technology "gear_dsp" into > > library "equipment", copied the object to a page, used ">" to > > push, selected all the pieces, pushed "c" to copy, "<" to pop, > > then pasted the copy on the page. > > This works, although there is an easier way, which is to go to the > library page, select the object (middle mouse button), then type > "C" for "copy", and you will see the object copied. For the sake of the archive, the key stroke is "shift-C". A un-shifted "c" will copy the object to the drawing. > I hope that addresses your issues, finally! Yup. It appears to have solved those, and I haven't found any more - yet. *hah* I've said it before, but it's worth repeating - _nothing_ works better than xcircuit for this type of a drawing. I'm competent using inkscape, gimp, qcad, xfig, and comfortable using at a few others. It doesn't do vector graphics like inkscape or sodipodi, bitmaps like gimp, dimensionally accurate layout like qcad - but when those specifics strengths aren't required, xcircuit is the best. Of course, that is just my opinion. *smiles* I used it for a plumbing system layout just last week. Anyway, all that to say "thanks". For your work, and for the open license. -- Philip _______________________________________________ Xcircuit-dev mailing list Xcircuit-dev@opencircuitdesign.com http://www.opencircuitdesign.com/mailman/listinfo/xcircuit-dev
