Re: [Kicad-developers] Migrating old designs best practice

The cache library and the rescue dialog should take care of this. 2017-11-23 5:02 GMT+01:00 hauptmech : > When opening an old design I noticed that the C and R symbol pin nodes > changed position (I'm guessing other symbols as well), breaking the > schematic. Did the people

[Kicad-developers] Migrating old designs best practice

When opening an old design I noticed that the C and R symbol pin nodes changed position (I'm guessing other symbols as well), breaking the schematic. Did the people who changed these symbols have a plan for migrating old designs? Is the 'rescue' supposed to handle this?

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

I understand this will break "forwards compatibility" if opening a v5 file from v4. and this break will be also 'silent' Sometimes such changes are unavoidable.point of views ... as I already pointed out I don't remember how many times, this changing is started for a wrong assumption: that 3D

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

I understand this will break "forwards compatibility" if opening a v5 file from v4. Sometimes such changes are unavoidable. On Thu, Nov 23, 2017 at 8:44 AM, easyw wrote: > This option is in fact a smooth transition for footprints... > but it will break the readability of new

Re: [Kicad-developers] Recent eeschema changes

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

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

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

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] [PATCH] Fix for 3D model offset

This option is in fact a smooth transition for footprints... but it will break the readability of new boards by previous release of kicad... no way back to previous releases, even to be just read... Which is better then? Library stuff are quite delicate to be touched IMO... On 11/22/2017 10:23

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

Wayne I still have an issue with silently breaking files. Using an "offset" parameter (but reading "at" for compatibility) does not break anyone's models and there is absolutely no confusion about which is mm and which is inches. Incidentally I think "offset" is a better name, it implies relative

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

On Wed, Nov 22, 2017 at 11:59 AM, Wayne Stambaugh wrote: > Yes, it is a change that will break some users 3D models > but I think the long term benefit outweighs the short term annoyance. It will break most of my boards. I won't complain because I appreciate the effort

Re: [Kicad-developers] [PATCH] Eeschema automatic manage junctions

Updated patchset for this proposal, rebased to master. I've also updated the commit messages to match the CHANGE:/NEW: format and added one new bug from launchpad that this addresses. -Seth On Wed, Nov 8, 2017 at 3:59 AM, Nick Østergaard wrote: > For that specific issue

Re: [Kicad-developers] Recent eeschema changes

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

> 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] [PATCH] Fix for 3D model offset

Hi Jose, I have several footprints that use manufacturer's models, where offsets and rotations are necessary. I really fail to see the point of breaking people's designs and libraries needlessly. this is probably quite common when a user needs some connector models for his/her production,

Re: [Kicad-developers] [PATCH] Drag components with line in Eeschema

Thanks Wayne! And no worries about tracking. As long as you don't mind the periodic pings, I don't mind waiting while more pressing issues are handled. -Seth On Wed, Nov 22, 2017 at 9:03 AM, Wayne Stambaugh wrote: > Hey Seth, > > Sorry, I'm losing track of the patches.

Re: [Kicad-developers] Recent eeschema changes

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] [PATCH] Drag components with line in Eeschema

Hey Seth, Sorry, I'm losing track of the patches. I committed the fix for this to the development branch. Thank you for your contribution. Cheers, Wayne On 11/22/2017 10:33 AM, Seth Hillbrand wrote: > Hi Wayne- > > Nope, different bug.  This one is a dragging issue, that one was like >

Re: [Kicad-developers] Recent eeschema changes

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

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] [PATCH] Drag components with line in Eeschema

Hi Wayne- Nope, different bug. This one is a dragging issue, that one was like merging. Best- Seth On Nov 22, 2017 7:15 AM, "Wayne Stambaugh" wrote: > Seth, > > Is this the patch you are talking about: > > commit b6884d3423cfddcf2e5f642c8a1928f4a86f748a > Author: Seth

Re: [Kicad-developers] New feature notifications

We could also set jenkins up to create an issue on the doc repo, triggered by the keyword, and then we can handle the documentation effort and discussion there. I can play with that. 2017-11-22 16:27 GMT+01:00 Maciej Sumiński : > On 11/22/2017 04:01 PM, Marco Ciampa

Re: [Kicad-developers] [PATCH] Allow items to be moved from all anchor points

Friendly bump, this bug is very annoying, related bug report https://bugs.launchpad.net/kicad/+bug/1722512 this patch fixes it. On Mon, Nov 20, 2017 at 10:29 AM, José Ignacio wrote: > A change in commit 57310001350 caused kicad to stop allowing users > to move items like

Re: [Kicad-developers] New feature notifications

On 11/22/2017 04:01 PM, Marco Ciampa wrote: > On Wed, Nov 22, 2017 at 02:55:35PM +0100, Maciej Sumiński wrote: >> On 11/22/2017 02:48 PM, Marco Ciampa wrote: >> [snip] >>> Please please please, >>> >>> when some new feature is accepted (code merged in master branch), either >>> write it in the dev

Re: [Kicad-developers] New feature notifications

On 11/22/2017 10:16 AM, Maciej Sumiński wrote: > On 11/22/2017 03:55 PM, Wayne Stambaugh wrote: >> On 11/22/2017 08:55 AM, Maciej Sumiński wrote: >>> On 11/22/2017 02:48 PM, Marco Ciampa wrote: >>> [snip] Please please please, when some new feature is accepted (code merged in master

Re: [Kicad-developers] New feature notifications

On 11/22/2017 03:55 PM, Wayne Stambaugh wrote: > On 11/22/2017 08:55 AM, Maciej Sumiński wrote: >> On 11/22/2017 02:48 PM, Marco Ciampa wrote: >> [snip] >>> Please please please, >>> >>> when some new feature is accepted (code merged in master branch), either >>> write it in the dev (master)

Re: [Kicad-developers] [PATCH] Drag components with line in Eeschema

Seth, Is this the patch you are talking about: commit b6884d3423cfddcf2e5f642c8a1928f4a86f748a Author: Seth Hillbrand Date: Fri Nov 17 08:35:20 2017 -0800 Eeschema: Improve wire merging CHANGED: wires now merge along the full length rather than just

Re: [Kicad-developers] [PATCH] Add live footprint filtering in modview window

Oliver, Here is the stack trace after typing 'r' in the search control. Thread 1 "kicad" received signal SIGSEGV, Segmentation fault. 0x7fffe0e3a250 in std::vector, std::allocator >

Re: [Kicad-developers] New feature notifications (was: Library Editor refactor)

On Wed, Nov 22, 2017 at 02:55:35PM +0100, Maciej Sumiński wrote: > On 11/22/2017 02:48 PM, Marco Ciampa wrote: > [snip] > > Please please please, > > > > when some new feature is accepted (code merged in master branch), either > > write it in the dev (master) branch of the documentation or

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

Consistency. Currently we have two separate units in kicad board and footprint files. This change unifies that issue. I know it's annoying but it is a decision that I made to make the file formatting more consistent. Yes, it is a change that will break some users 3D models but I think the long

Re: [Kicad-developers] New feature notifications

On 11/22/2017 08:55 AM, Maciej Sumiński wrote: > On 11/22/2017 02:48 PM, Marco Ciampa wrote: > [snip] >> Please please please, >> >> when some new feature is accepted (code merged in master branch), either >> write it in the dev (master) branch of the documentation or somewhere to >> enable doc

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

I have several footprints that use manufacturer's models, where offsets and rotations are necessary. I really fail to see the point of breaking people's designs and libraries needlessly. On Nov 22, 2017 7:07 AM, "Wayne Stambaugh" wrote: > What is wrong with just reading

Re: [Kicad-developers] terms clarification

These are the accepted terms and should be used for UI strings. At some point when I have nothing better to do, I will update the source code terminology so that these two terms are used everywhere. On 11/22/2017 08:31 AM, Oliver Walters wrote: > +1 for "symbol" and "footprint" > > On Thu, Nov

Re: [Kicad-developers] New feature notifications (was: Library Editor refactor)

On 11/22/2017 02:48 PM, Marco Ciampa wrote: [snip] > Please please please, > > when some new feature is accepted (code merged in master branch), either > write it in the dev (master) branch of the documentation or somewhere to > enable doc writers to describe the new feature... (wiki? txt in the

Re: [Kicad-developers] terms clarification

On Wed, Nov 22, 2017 at 02:42:05PM +0100, jp charras wrote: > Le 22/11/2017 à 14:28, Marco Ciampa a écrit : > > On Wed, Nov 22, 2017 at 08:14:02AM -0500, Wayne Stambaugh wrote: > >> The devs discussed this some time ago and the general consensus is that > >> symbol is the preferred term. I've

Re: [Kicad-developers] Library Editor refactor

On Wed, Nov 22, 2017 at 02:39:16PM +0100, Maciej Sumiński wrote: > On 11/22/2017 02:28 PM, jp charras wrote: > > Le 21/11/2017 à 23:49, Maciej Suminski a écrit : > >> I have just managed to fix the last issue (disappearing buttons in 'Save > >> Library' dialog) and pushed the code to the master

Re: [Kicad-developers] terms clarification

Le 22/11/2017 à 14:28, Marco Ciampa a écrit : > On Wed, Nov 22, 2017 at 08:14:02AM -0500, Wayne Stambaugh wrote: >> The devs discussed this some time ago and the general consensus is that >> symbol is the preferred term. I've already started converting the UI >> strings to use the term symbol.

Re: [Kicad-developers] terms clarification

I wonder if there is a distinction in naming an instance and its model, like object vs class in C++. On 11/22/2017 02:31 PM, Oliver Walters wrote: > +1 for "symbol" and "footprint" > > On Thu, Nov 23, 2017 at 12:28 AM, Marco Ciampa wrote: > >> On Wed, Nov 22, 2017 at

Re: [Kicad-developers] Library Editor refactor

On 11/22/2017 02:28 PM, jp charras wrote: > Le 21/11/2017 à 23:49, Maciej Suminski a écrit : >> I have just managed to fix the last issue (disappearing buttons in 'Save >> Library' dialog) and pushed the code to the master branch. >> >> Thank you for testing and comments, I really appreciate it.

Re: [Kicad-developers] terms clarification

+1 for "symbol" and "footprint" On Thu, Nov 23, 2017 at 12:28 AM, Marco Ciampa wrote: > On Wed, Nov 22, 2017 at 08:14:02AM -0500, Wayne Stambaugh wrote: > > The devs discussed this some time ago and the general consensus is that > > symbol is the preferred term. I've already

Re: [Kicad-developers] terms clarification

On Wed, Nov 22, 2017 at 08:14:02AM -0500, Wayne Stambaugh wrote: > The devs discussed this some time ago and the general consensus is that > symbol is the preferred term. I've already started converting the UI > strings to use the term symbol. I'm sure there are UI strings that I > missed. If

Re: [Kicad-developers] Library Editor refactor

Le 21/11/2017 à 23:49, Maciej Suminski a écrit : > I have just managed to fix the last issue (disappearing buttons in 'Save > Library' dialog) and pushed the code to the master branch. > > Thank you for testing and comments, I really appreciate it. Now let's > have a look at the abandoned patches

Re: [Kicad-developers] Library Editor refactor

> Regarding the window title, I consider library selected after opening a > part. Do you suggest that highlighting a library (single click) in the > component tree should make it selected? I wonder if there is any benefit > of doing so. > Ah I see that it does put the right text into the title

Re: [Kicad-developers] Library Editor refactor

Hi Oliver, Thank you for the report. It should be fixed already. Regarding the window title, I consider library selected after opening a part. Do you suggest that highlighting a library (single click) in the component tree should make it selected? I wonder if there is any benefit of doing so.

Re: [Kicad-developers] [PATCH] Add live footprint filtering in modview window

I already removed the patches from my dev branch so I could work on my stuff. I will try to get a stack dump when I get a chance. On 11/22/2017 07:33 AM, Oliver Walters wrote: > Wayne, > > That's disappointing. Any further debug info you can provide? > > On Wed, Nov 22, 2017 at 11:31 PM, Wayne

Re: [Kicad-developers] terms clarification

The devs discussed this some time ago and the general consensus is that symbol is the preferred term. I've already started converting the UI strings to use the term symbol. I'm sure there are UI strings that I missed. If you find them, please let me know so I can correct them. Cheers, Wayne

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

What is wrong with just reading the footprint in mm rather than converting from decimils from now on? It's only going to be a one time issue when a user adds a footprint that has not been converted to mm to a board. On 11/22/2017 06:16 AM, Oliver Walters wrote: > Wayne, > > > I believe he has

[Kicad-developers] terms clarification

Hello devs, sorry for boring with (what seems to be) trivial things... In the KiCad program the terms "part" and "component" are used extensively in a way that seems to be equivalent. Are these terms really synonimous? If this is the case, why not settle for _one_ term to semplify life to

Re: [Kicad-developers] Recent eeschema changes

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] [PATCH] Fix for 3D model offset

On 11/22/2017 04:25 AM, easyw wrote: > Hi Wayne, >> I'm not sure I understand what the issue is.  Once an offset is changed >> to mm when either a footprint in a board or a library is parsed, why >> would it not be saved as mm.  If it isn't, then this is a bug.  Once the >> footprint offset is

Re: [Kicad-developers] Recent eeschema changes

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] [Question] - Artist Credits

Simon, In that case I think this information should be nixed entirely. It serves no real purpose to include front-and-center in the about screen. All that info can be gleaned from the library repositories if users are really interested. On Wed, Nov 22, 2017 at 11:36 PM, Simon Wells

Re: [Kicad-developers] Polygons: should have outline mode to draw Edge.Cuts

On 22/11/17 13:35, Wayne Stambaugh wrote: > Henner, > > AFAIK, no one is working on any more changes to the polygon tool. I am > planning on announcing the stable 5 feature freeze sometime over the > Thanksgiving holiday so if it's not ready by then, it will have to wait > for the next

Re: [Kicad-developers] [Question] - Artist Credits

The only way I can see any of that information staying relevant is if it is collated at run time from a text file or something in each of the individual repos that are used, that way when someone submits a lib they can include a name in the text file if they so wish, and then the about code

Re: [Kicad-developers] Polygons: should have outline mode to draw Edge.Cuts

Henner, AFAIK, no one is working on any more changes to the polygon tool. I am planning on announcing the stable 5 feature freeze sometime over the Thanksgiving holiday so if it's not ready by then, it will have to wait for the next development version. Cheers, Wayne On 11/21/2017 12:42 AM,

Re: [Kicad-developers] [PATCH] Add live footprint filtering in modview window

Wayne, That's disappointing. Any further debug info you can provide? On Wed, Nov 22, 2017 at 11:31 PM, Wayne Stambaugh wrote: > Oliver, > > I tested your footprint filtering patch set last night and it didn't go > very well. The very first letter I typed ('r') in the

Re: [Kicad-developers] [PATCH] Add live footprint filtering in modview window

Oliver, I tested your footprint filtering patch set last night and it didn't go very well. The very first letter I typed ('r') in the filter control caused kicad to crash so it's not ready just yet. Cheers, Wayne On 11/20/2017 06:57 PM, Oliver Walters wrote: > Wayne, > > Friendly bump in

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

I believe he has a point. The footprint files do not have version information so if you load and save a footprint multiple times, the "offset" (if non zero) will continuously be multiplied by 2.54x This is not true if the footprint importer will be patched to read the data as mm from now on...

Re: [Kicad-developers] Recent eeschema changes

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

Re: [Kicad-developers] Library Editor refactor

Orson, I have found another potential issue (only a small one!) If you add a new library but then cancel, it triggers an assert on debug builds: To reproduce: 1. Press "Add an existing library" 2. Select a library from the file chooser 3. On the dialog that says "Choose the library table to

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

Wayne, I believe he has a point. The footprint files do not have version information so if you load and save a footprint multiple times, the "offset" (if non zero) will continuously be multiplied by 2.54x I think there are two ways forward: 1. Revert my patch and live with the file format unit

Re: [Kicad-developers] Some tests.

Hi, As an interest. I tested now with that A64-Olinuxino board. Result is: Old algo with parallel zone filling 8s. That 2 times fill algo. New algo with parallel zone filling 20s. Only fill can be done parallel, not insulated area cleaning. Filling take approx 2s. Current master branch 37s.

[Kicad-developers] [Question] - Artist Credits

In the "About" dialog, under the "Artists" tab, I note that Christophe Boschat and Renie Marquet are credited with creation of the 3D models. I believe this is very outdated information, and there have been a few high value contributors of 3D model data in the library repositories. Unless anyone

Re: [Kicad-developers] Library Editor refactor

Orson, The new symbol editor is looking great! One small issue I have found: The window title bar reads "Symbol library editor - no library selected" no matter which library is currently selected. I think this needs to be updated to report the currently selected library. Thanks, On Wed, Nov

Re: [Kicad-developers] Library Editor refactor

2017-11-22 9:19 GMT+01:00 Maciej Sumiński : > Hi Nick, > > On 11/22/2017 12:04 AM, Nick Østergaard wrote: > > Thank your for fixing. Seems to address the issue. Some minor things > about > > it. > > > > It seems that it adds about two lines of whitespace inside that box

Re: [Kicad-developers] [PATCH] Drag components with line in Eeschema

Friendly ping. Small patch but fixes annoying behavior. Let me know if there are any questions. Best- Seth On Wed, Nov 15, 2017 at 2:59 PM, Seth Hillbrand wrote: > ​The attached patch fixes > https://bugs.launchpad.net/kicad/+bug/1167714 > > This happens when you

Re: [Kicad-developers] [PATCH] Fix for 3D model offset

Hi Wayne, I'm not sure I understand what the issue is. Once an offset is changed to mm when either a footprint in a board or a library is parsed, why would it not be saved as mm. If it isn't, then this is a bug. Once the footprint offset is converted to mm, there should be no expectation that

Re: [Kicad-developers] Library Editor refactor

Hi Nick, On 11/22/2017 12:04 AM, Nick Østergaard wrote: > Thank your for fixing. Seems to address the issue. Some minor things about > it. > > It seems that it adds about two lines of whitespace inside that box where > the checkboxes are, even if I edit more libs. Do you mean *less* libraries?

[Kicad-developers] Recent eeschema changes

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