Re: [Kicad-developers] Component fields use case

2011-09-01 Thread Fred Cooke
LOL, the fact that you won't read this email makes it so much more satisfying to write! Adios, Dick! :-) On Fri, Sep 2, 2011 at 9:39 AM, Dick Hollenbeck wrote: > Fred, > > Welcome to my spam filter. > > Dick > > ___ Mailing list: https://launchpad.net/

Re: [Kicad-developers] [PATCH] Centralized paneinfo

2011-09-01 Thread Wayne Stambaugh
On 9/1/2011 12:04 PM, hauptmech wrote: > >> I found an issue with this patch. Take a look at last horizontal tool bar >> button in the attached image. This problem also exists in the EESchema, >> library editor, cvpcb, cvpcb footprint viewer, pcbnew, and module editor main >> windows. It appear

Re: [Kicad-developers] [PATCH] Centralized paneinfo

2011-09-01 Thread hauptmech
> I found an issue with this patch. Take a look at last horizontal tool bar > button in the attached image. This problem also exists in the EESchema, > library editor, cvpcb, cvpcb footprint viewer, pcbnew, and module editor main > windows. It appears to effect both horizontal and vertical tool

Re: [Kicad-developers] Component fields use case

2011-09-01 Thread Fred Cooke
You can't improve anything without making changes, Dick. And his point re breaking the API that exists (he's not the only one who has scripts against your text files and prefers kicad for text file storage reasons) is valid. Why the unpleasant attitude? :-/ On Thu, Sep 1, 2011 at 3:51 PM, Dick Hol

Re: [Kicad-developers] Component fields use case

2011-09-01 Thread Dick Hollenbeck
On 09/01/2011 03:33 AM, hauptmech wrote: >> libraries from what they are now to > key-value pairs in a new file format. And I can deal with that file > format not handling null strings. > > But it's a bit rough on those of us using kicad to pull the rug out from > underneath us

Re: [Kicad-developers] Component fields use case

2011-09-01 Thread Wayne Stambaugh
On 9/1/2011 1:28 AM, Dick Hollenbeck wrote: > > Proposal: > > Are you ok with licensing this work under GPL? If so, can we check these > into a > contrib directory or something, as part of the tree, along with a readme.txt > or > readme.html file? > > (Although I think that posting which talk

Re: [Kicad-developers] Component fields use case

2011-09-01 Thread Brian Sidebotham
On 1 September 2011 06:28, Dick Hollenbeck wrote: > > Proposal: > > Are you ok with licensing this work under GPL?  If so, can we check these > into a > contrib directory or something, as part of the tree, along with a readme.txt > or > readme.html file? > > (Although I think that posting which

Re: [Kicad-developers] [PATCH] Centralized paneinfo

2011-09-01 Thread Wayne Stambaugh
On 9/1/2011 6:06 AM, hauptmech wrote: > Attached is a patch proposal for centralizing the configuration of Aui > panes in prep for a user configurable interface. > > The outward GUI remains unchanged. When we are ready to allow moveable > toolbars, a quick change to the EDA_PANEINFO class, already

Re: [Kicad-developers] Component fields use case

2011-09-01 Thread Wayne Stambaugh
On 9/1/2011 4:33 AM, hauptmech wrote: >> libraries from what they are now to > key-value pairs in a new file format. And I can deal with that file > format not handling null strings. > > But it's a bit rough on those of us using kicad to pull the rug out from > underneath us by

Re: [Kicad-developers] Duplicate schematic sheet names.

2011-09-01 Thread Wayne Stambaugh
On 8/31/2011 7:00 PM, Andy Peters wrote: > On Aug 31, 2011, at 1:26 PM, Fred Cooke wrote: > >> While we're on the subject of file formats, PLEASE, stop updating time >> stamps in the header/comment when NOTHING else has changed. I can show you >> commits to hw repositories with 30 eroneous files c

[Kicad-developers] [PATCH] Centralized paneinfo

2011-09-01 Thread hauptmech
Attached is a patch proposal for centralizing the configuration of Aui panes in prep for a user configurable interface. The outward GUI remains unchanged. When we are ready to allow moveable toolbars, a quick change to the EDA_PANEINFO class, already prepped, will do this. * Added EDA_PANEINFO cl

Re: [Kicad-developers] Component fields use case

2011-09-01 Thread hauptmech
> libraries from what they are now to > >>> key-value pairs in a new file format. And I can deal with that file > >>> format not handling null strings. > >>> > >>> But it's a bit rough on those of us using kicad to pull the rug out from > >>> underneath us by jiggering the existing file format. If