On 12/28/2017 06:25 PM, Andy Peters wrote: > On Nov 18, 2017, at 6:07 AM, Wayne Stambaugh <[email protected] > <mailto:[email protected]>> wrote: >> >> Diego, >> >> Thank you for the offer but I'm already working on it. It is not as >> easy to fix as it would seem. The problem is what to do when you do not >> have write access to the library with the invalid characters. I have a >> few ideas but it will take me a while to get it the way I want it. > > Hi, Wayne, > > I just ran into this problem. (I’m using the Dec 24 nightly on a High > Sierra Mac.) The thing is that my libraries are in a directory to which > Kicad should have write access. On my Mac, they’re at > ~/Library/Application Support/kicad/library > > The three parts in my library that use a forward-slash in the name are > new for a design I am still working on, so renaming them in the library > and then replacing the components on the schematic from the library > isn’t too painful. That said: should “policy” going forward be to simply > not have slashes in part names? I guess this is probably wise, since as > I understand it, the .sweet format will be like .pretty with one symbol > per file and the file’s name is the symbol name. > > -a
In the short term, we will have to disallow the '/' character in symbol names just like we do in footprint names. This was done with footprint names because the file name is the footprint name and '/' is a path separator. I may change this during version 6 development by using the internal symbol/footprint name ( there is support for this in footprint file format) rather than the file name and escape the '/' and ':' characters so that any character >=0x20 should be valid in symbol and footprint names. This change will not be backwards compatible but I think it's a better solution than what we are currently doing. > >> >> On 11/18/2017 08:00 AM, Diego Herranz wrote: >>> Thanks. I'll chase that bug. >>> >>> Diego >>> >>> On 18 Nov 2017 11:35 am, "Nick Østergaard" <[email protected] >>> <mailto:[email protected]> >>> <mailto:[email protected]>> wrote: >>> >>> See https://bugs.launchpad.net/bugs/1732236 >>> <https://bugs.launchpad.net/bugs/1732236> >>> >>> 2017-11-18 11:42 GMT+01:00 Diego Herranz >>> <[email protected] >>> <mailto:[email protected]> >>> <mailto:[email protected]>>: >>> >>> Hi, >>> >>> I'm testing a recent build (41f9c19b) on Ubuntu 16.04 64 bits. >>> >>> When opening a schematic made with a nightly build ~2 months >>> old, the remapping dialog shows up. So far so good. >>> >>> I've followed the recommendations >>> in http://kicad-pcb.org/post/symbol-lib-table/ >>> <http://kicad-pcb.org/post/symbol-lib-table/> and most things >>> seem to be working fine. Every symbol gets remapped but 2. Both >>> of which include '/' in their name (e.g. PIC32MX110F016D-I/PT). >>> >>> Opening the schematic after the remap, it seems Kicad has >>> changed it to PIC32MX110F016D-I_PT. >>> >>> In fact, after a bit more searching, I've found out that as soon >>> as the remapping dialog shows up, before clicking on "Remap >>> symbols" the '/' characters have been replaced to '_'. So I'm >>> guessing that is the reason why it can't find the symbols when >>> remapping? >>> "Warning: No symbol 'PIC32MX110F016D-I_PT' found in symbol >>> library table." confirms that the name was changed before the >>> remapping attempt. >>> >>> I have then tried to edit the broken symbols in Eeschema. When I >>> try to assign "PIC32MX110F016D-I/PT" again, which can be found >>> through the "Choose Symbol" dialog without problems, it complains: >>> " Symbol 'PIC32MX1XXFXXXD-I_PT' not found in library >>> 'MCU_Microchip_PIC32'! " >>> >>> Am I doing something wrong? Is this a bug? >>> >>> Many thanks, >>> Diego >>> >>> _______________________________________________ >>> Mailing list: https://launchpad.net/~kicad-developers >>> <https://launchpad.net/~kicad-developers> >>> Post to : [email protected] >>> <mailto:[email protected]> >>> <mailto:[email protected]> >>> Unsubscribe : https://launchpad.net/~kicad-developers >>> <https://launchpad.net/~kicad-developers> >>> More help : https://help.launchpad.net/ListHelp >>> <https://help.launchpad.net/ListHelp> >>> > > > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : [email protected] > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
