kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #33499
Re: spaces not allowed in SCH library nicknames
It is a great idea. I hope it pans out….
> On 26 Jan 2018, at 22:00, Wayne Stambaugh <stambaughw@xxxxxxxxx> wrote:
>
> Seth,
>
> I haven't had a chance to test it but it's a clever concept. I would
> prefer a bunch user testing on this before I merge it. If I do decide
> to merge it, we should probably restore allowing spaces in symbol
> library nicknames. As of now, this patch doesn't buy us much if we
> don't change that as well.
>
> Cheers,
>
> Wayne
>
> On 01/26/2018 03:00 PM, Seth Hillbrand wrote:
>> Wayne-
>>
>> Would you object to a patch like the attached? It reads the name line
>> in reverse order, allowing spaces in the component name. If this is an
>> acceptable approach, I'll make the other required internal changes.
>>
>> -Seth
>>
>> 2018-01-26 10:22 GMT-08:00 Tomasz Wlostowski <tomasz.wlostowski@xxxxxxx <mailto:tomasz.wlostowski@xxxxxxx>
>> <mailto:tomasz.wlostowski@xxxxxxx <mailto:tomasz.wlostowski@xxxxxxx>>>:
>>
>> On 26/01/18 19:18, Wayne Stambaugh wrote:
>>> On 1/26/2018 1:01 PM, Tomasz Wlostowski wrote:
>>>> Hi all,
>>>>
>>>> Why are space characters not allowed in the SCH library nicknames, but
>>>> are OK for the FP libraries? Is this an overlook on SCH/PCB side?
>>>>
>>>> I'd like to disable the space check in eeschema, it's very annoying if
>>>> the library file names contain spaces.
>>>>
>>>> Regards,
>>>> Tom
>>>
>>> For the same reason you can have spaces in symbol names, library symbol
>>> names are not quoted in the schematic file format. If you can figure
>>> out a way to fix this without changing the schematic file format and
>>> breaking anything, then I'm ok with that. The new schematic file format
>>> will use quoted strings for symbol library links (which will only be for
>>> reverting or updating since symbols will be embedded in the schematic)
>>> so I will remove this restriction once the new file formats are in play.
>>>
>>
>> Hi Wayne,
>>
>> Now I understand the reason for not allowing spaces. What about the
>> slashes?
>>
>> Tom
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> <https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>>
>> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>> <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>>
>> Unsubscribe : https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
>> <https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>>
>> More help : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>
>> <https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>>
>>
>>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> Unsubscribe : https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
> More help : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>
Follow ups
References