On 23.02.2012 23:18, Dick Hollenbeck wrote:
>>
>> Unfortunately, when a hand modified component is re-imported into the
>> library editor, and saved, most of previous efforts to sort pins are
>> void, which makes the .lib file difficult to read back.
>>
>
> Of course, a person could want the pins sorted by spatial location, or not
want them
> sorted at all, keeping order of entry.
>
Actually sort key and order doesn't matter. Problem is that lines in KiCAD files
are intermixed after load-and-save (even without any modification by user in
KiCAD itself). It makes using of version control systems less useful. Same about
storing modules in library - why modified module moved into the end of library
file? Diff utility can't find particular change after that. And why this
behavior is different in schematic and modules libraries (in schematic library
elements, thanks God, are sorted)? Why new module appended to the file while
it's name inserted into $INDEX section in alphabetical order? Is seems like
instead of code re-using developers re-invent new wheel for any particular piece
of code.
If KiCAD files could keep their lines order after load-modify-save, Laurent
problem will be solved automatically - he can sort lined in any preferable order
once.
--
Regards,
Sergey A. Borshch mailto: sb...@sourceforge.net
SB ELDI ltd. Riga, Latvia
_______________________________________________
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
