Hi Tim,

Thank you! This makes quite a bit more sense now.

On 12/26/20 11:13 AM, Tim Edwards wrote:
Make sure you understand the difference between a library page and a
technology.  They were originally the same thing in xcircuit, which makes
it a bit more confusing.

All objects are considered individually.  If they have the same prefix,
which is in the form of a Tcl namespace with a double colon ("::") between
the prefix and the object name, then the namespace prefix is called the
"technology", and all objects belonging to the same technology are
considered grouped together.  If you do "Save Technology" from the File
menu, then all objects with then you can select from among all the
technology prefixes and save all those objects as a ".lps" library file.

I know this was discussed in the reference manual (http://opencircuitdesign.com/xcircuit/features.html), but what you wrote me here made more sense to me.

The default technology namespace has an empty prefix, or just "::" (this
is also a Tcl thing).  If you create an object with the "M" key, and
just give it a plain name, then it gets grouped in this default "(user)"
technology.

What I was missing was the 'M' key. The 'Creating New Objects' hyperlink (to anchor '#New Objects') is broken, and so the 'M' key was what I was having a lot of difficulty finding.

But as I said, every object is considered individually, and there is
nothing that distinguishes one technology from another apart from that
name prefix.  So if you want to put a number of objects into their own
technology, then you can just rename the prefixes of the ones you want.
That's what the "e" key is for.  But for the "e" key to work, you need to
have the pointer on top of the name of the object.  Then when it is
being edited, you will see both the technology prefix, the "::" namespace
separator, and the object name.

Now that I put the cursor on the label, the 'e' button works. The text tool behaves similarly, but I don't think I thought to try that.

If I missed explaining anything, please let me know!

Is there a way you prefer patches to the HTML documentation?

Thanks,
Kevin

_______________________________________________
Xcircuit-dev mailing list
Xcircuit-dev@opencircuitdesign.com
http://www.opencircuitdesign.com/mailman/listinfo/xcircuit-dev

Reply via email to