Re: [Kicad-developers] Recent eeschema changes

2017-11-23 Thread Wayne Stambaugh
On 11/22/2017 10:42 PM, hauptmech wrote: > On 23/11/17 10:51, Wayne Stambaugh wrote: >> On 11/22/2017 4:46 PM, hauptmech wrote: >>> On 23/11/17 07:03, Julius Schmidt wrote: On Wed, 22 Nov 2017, Andy Peters wrote: > This “touching” of projects occurs with more applications than I can

Re: [Kicad-developers] Recent eeschema changes

2017-11-23 Thread Marco Ciampa
On Wed, Nov 22, 2017 at 12:04:10PM -0500, Kevin Cozens wrote: > On 2017-11-22 03:16 AM, Julius Schmidt wrote: > >It seems the current origin/master will modify schematic files on disk > >just by opening them -- even if I opt out of the remap tool. > > There is also another subtle bug you can hit

Re: [Kicad-developers] Recent eeschema changes

2017-11-22 Thread Wayne Stambaugh
It already does that. The schematic is back up to it's normal backup file name. It doesn't back up the project file which I need do need to add. On 11/22/2017 4:57 PM, Ben Hest wrote: > I haven't looked at exactly what's going on during the conversion, but > would it make sense to provide for a

Re: [Kicad-developers] Recent eeschema changes

2017-11-22 Thread Ben Hest
I haven't looked at exactly what's going on during the conversion, but would it make sense to provide for a special pre-conversion backup file of the schematic when the remapping process happens? On Wed, Nov 22, 2017 at 3:51 PM, Wayne Stambaugh wrote: > On 11/22/2017 4:46

Re: [Kicad-developers] Recent eeschema changes

2017-11-22 Thread Wayne Stambaugh
On 11/22/2017 4:46 PM, hauptmech wrote: > On 23/11/17 07:03, Julius Schmidt wrote: >> On Wed, 22 Nov 2017, Andy Peters wrote: >> >>> This “touching” of projects occurs with more applications than I can >>> count. For example: every time I want to view a completed Altium >>> project and I change

Re: [Kicad-developers] Recent eeschema changes

2017-11-22 Thread hauptmech
On 23/11/17 07:03, Julius Schmidt wrote: On Wed, 22 Nov 2017, Andy Peters wrote: This “touching” of projects occurs with more applications than I can count. For example: every time I want to view a completed Altium project and I change layer visibility, Altium marks the layout as modified.

Re: [Kicad-developers] Recent eeschema changes

2017-11-22 Thread Julius Schmidt
On Wed, 22 Nov 2017, Andy Peters wrote: This “touching” of projects occurs with more applications than I can count. For example: every time I want to view a completed Altium project and I change layer visibility, Altium marks the layout as modified. It asks me if I want to save the file

Re: [Kicad-developers] Recent eeschema changes

2017-11-22 Thread Andy Peters
> On Nov 22, 2017, at 8:35 AM, Julius Schmidt wrote: > > > On Wed, 22 Nov 2017, Wayne Stambaugh wrote: > >> First of all, you cannot opt out of remapping you schematic and expect >> the library symbol links to continue to work correctly. The symbol >> library table is now

Re: [Kicad-developers] Recent eeschema changes

2017-11-22 Thread Kevin Cozens
On 2017-11-22 03:16 AM, Julius Schmidt wrote: It seems the current origin/master will modify schematic files on disk just by opening them -- even if I opt out of the remap tool. There is also another subtle bug you can hit that involves the remap process and how it modifies the project files

Re: [Kicad-developers] Recent eeschema changes

2017-11-22 Thread Wayne Stambaugh
On 11/22/2017 10:35 AM, Julius Schmidt wrote: > > On Wed, 22 Nov 2017, Wayne Stambaugh wrote: > >> First of all, you cannot opt out of remapping you schematic and expect >> the library symbol links to continue to work correctly.  The symbol >> library table is now the only way that library

Re: [Kicad-developers] Recent eeschema changes

2017-11-22 Thread Julius Schmidt
On Wed, 22 Nov 2017, Wayne Stambaugh wrote: First of all, you cannot opt out of remapping you schematic and expect the library symbol links to continue to work correctly. The symbol library table is now the only way that library symbols are linked to schematics symbols. The only reason any

Re: [Kicad-developers] Recent eeschema changes

2017-11-22 Thread Maciej Sumiński
On 11/22/2017 01:56 PM, Wayne Stambaugh wrote: [snip] > No it didn't. You were just lucky. IMO, the symbol cache library has > always been a disaster waiting to happen and it masked a lot of issues > with broken and modified symbol libraries. Your desire to have a single > symbol footprint link

Re: [Kicad-developers] Recent eeschema changes

2017-11-22 Thread Wayne Stambaugh
On 11/22/2017 03:16 AM, Julius Schmidt wrote: > It seems the current origin/master will modify schematic files on disk > just by opening them -- even if I opt out of the remap tool. This is > rather undesirable behaviour, I don't want files to become unreadable by > the original version that

Re: [Kicad-developers] Recent eeschema changes

2017-11-22 Thread Nick Østergaard
Have you read http://kicad-pcb.org/post/symbol-lib-table/? 2017-11-22 9:16 GMT+01:00 Julius Schmidt : > It seems the current origin/master will modify schematic files on disk > just by opening them -- even if I opt out of the remap tool. This is rather > undesirable behaviour, I

[Kicad-developers] Recent eeschema changes

2017-11-22 Thread Julius Schmidt
It seems the current origin/master will modify schematic files on disk just by opening them -- even if I opt out of the remap tool. This is rather undesirable behaviour, I don't want files to become unreadable by the original version that created them just because I *opened* them. I am also