kicad-developers team mailing list archive

[jp charras <jp.charras@xxxxxxxxxx>]

Le 19/09/2013 17:37, Wayne Stambaugh a écrit :
...
> I've never liked the fact the Eeschema is case insensitive so you'll get
> no argument from me.  It's just been that way since I've joined the
> project.  Changing it surely will break some existing projects and
> libraries.  There is only one way to find out how many things will get
> broken.  That's one of the reason's I never tackled the problem.  I
> didn't want to know the answer to that question :).  If you feel up to
> it, by all means make Eeschema case sensitive.
> 
>>
>> Certainly fixing eeschema will break designs,  unless somebody can think
>> of a fix point where eeschema can heal the design.
>>
>> Dick.
>>
>>>
>>> Also, in cmake there is a KICAD_KEEPCASE option (default off) which
>>> could be related to/a fix for this.

Due to the new .pretty lib format which imply a case sensitive footprint
name, Kicad is currently moving to the case sensitive option.
I have no problem with that.

KICAD_KEEPCASE option ON could be the default option (in fact removed).

This change will have some (minor) issues which are already existing for
footprint names.
To avoid annoying issues in eeschema, a case sensitive search in libs
could be made first, and only for not found components, a case
insensitive search could be made with an automatic update of component
lib names if found, when a schematic is loaded, and also when the user
want to place a new component.

This is one of things which are on my todo list, but if there is a
volunteer to do that ...


-- 
Jean-Pierre CHARRAS