Hello Philip,
I have 10 Schematics, into all a Schematics i have PMOS1.
I wand to change PMOS1 to PMOS2 in All a Schematics. So far I'm
failing to find an elegant way to do this.
I think I would look at a text editor. The .ps file is a flat text
file so emacs, vim, or another good text editor should be able to
do a search and replace for the block of text that is PMOS1.
Still, in the interest of a more normal user interface where problems
can be solved within the tool instead of offline with a text editor,
I have added a command option "instance [selected] object [<name>]",
where without the extra argument "<name>", xcircuit prints the object
name of all the selected instances (this was the previous behavior),
but with the extra argument "<name>", xcircuit changes the instance
to use the object named <name> (which is the new behavior I just
added).
To go along with the new command, there is a menu option "Edit->Replace"
with a pop-up dialog so that you can select many instances and replace
them all with a different object.
The new command is only relevant to the Tcl/Tk-enabled version of
xcircuit. The new code is immediately available using "git", and the
new tarball will be created overnight.
In conjunction with the other recent discussion, note that in this
case the existing object was "analoglib3::pMOS1", and the object to
replace it was "analog::pmos2". The whole name including the
technology prefix needs to be replaced, and xcircuit is not helping
matters by hiding the technology prefix.
Also note that because xcircuit saves the definitions of only the
objects used in a drawing, doing the text replacement creates a file
that is invalid outside of xcircuit, because once the replacement is
made, the new object "pmos2" is undefined in the file, so running
ghostscript or ps2pdf will generate an error. The text change has
to be followed up by reading the file into xcircuit and writing it
back out again. Since all of that is pretty non-obvious to anyone
not familiar with the xcircuit output format, I think the menu-driven
function is the better solution.
Regards,
Tim
+--------------------------------+-------------------------------------+
| R. Timothy Edwards (Tim) | email: t...@opencircuitdesign.com |
| Open Circuit Design | web: http://opencircuitdesign.com |
| 22815 Timber Creek Lane | phone: (301) 528-5030 |
| Clarksburg, MD 20871-4001 | cell: (240) 401-0616 |
+--------------------------------+-------------------------------------+
_______________________________________________
Xcircuit-dev mailing list
Xcircuit-dev@opencircuitdesign.com
http://www.opencircuitdesign.com/mailman/listinfo/xcircuit-dev
