I'm not sure what m_oldRootName is for. I believe JP added that. Perhaps he could shed some light this.
Wayne On 11/22/2010 1:03 PM, Marco Mattila wrote: > Ok, but what was the bug/issue that was fixed by introducing > m_oldRootName? Before 2559 it was possible to create a copy of a > component by changing the value field and clicking save. Replacing a > component was done by creating a copy first and then deleting the old > one. After introducing m_oldRootName that's not possible anymore. > > marco > > On Mon, Nov 22, 2010 at 6:42 PM, Wayne Stambaugh <stambau...@verizon.net> > wrote: >> I cannot comment on the behavior Karl described. I can tell you that >> this issue has been a on going problem due to the current library and >> component designs. A couple of not particularly elegant solutions is to >> save the component to a new library and rename it or export it and >> change the name and import back into the current library. There >> probably should be a way to copy an existing component and giving it a >> new name but that would require some coding. Obviously, if you are >> making an identical copy of a component using an alias makes more sense. >> I don't know how much effort I would be willing to spend on this as >> Dick and I are collaborating on the new library and part s-expression >> format which will make this problem go away. >> >> Wayne >> > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp