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

Thanks for the tip. I'll use it to check schematics wiring. Diego On Sun, Nov 26, 2017 at 6:53 PM, jp charras wrote: > Le 26/11/2017 à 19:15, Diego Herranz a écrit : > > It's interesting that only happen if I rescue symbols. > > > > Anyway, thanks for the help and I'll

Re: [Kicad-developers] [PATCH] Prevent multiple item delete when routing (fixes lp:1715158)

THANK YOU On Wed, Dec 6, 2017 at 10:13 PM, Seth Hillbrand wrote: > ​The attached patch corrects https://bugs.launchpad.net/kicad/+bug/1715158 > where pressing delete in pcbnew GAL canvas will delete _both_ a wire​ and > the footprint underneath it. > > I know that this

[Kicad-developers] [PATCH] Prevent multiple item delete when routing (fixes lp:1715158)

​The attached patch corrects https://bugs.launchpad.net/kicad/+bug/1715158 where pressing delete in pcbnew GAL canvas will delete _both_ a wire​ and the footprint underneath it. I know that this bug was marked "triaged" but it bit me on a board and I didn't notice the missing footprint (was

[Kicad-developers] [PATCH] spectra export filename (fixes lp:1736724)

This corrects the parameters for wxFileSelector in the ExportToSpectra() function. Fixes https://bugs.launchpad.net/kicad/+bug/1736724 -S From 18bb5b432aeee47b908b0094f48490025fbfe46a Mon Sep 17 00:00:00 2001 From: Seth Hillbrand Date: Wed, 6 Dec 2017 17:18:35 -0800

Re: [Kicad-developers] [PATCH 0/6] A few compatibility fixes

On Wed, Dec 06, 2017 at 11:53:09PM +, Wayne Stambaugh wrote: > On 12/06/2017 06:42 PM, Chris Pavlina wrote: > > On Wed, Dec 06, 2017 at 11:38:21PM +, Wayne Stambaugh wrote: > >> Simon, > >> > >> I'm OK with most of these patches but since when is it invalid to > >> initialize a c array in

Re: [Kicad-developers] [PATCH] Fix artifacts on touchpad scroll (fixes lp:1735669)

Seth, I merged this patch so we could get some widespread testing done on it. Thanks, Wayne On 12/04/2017 07:45 PM, Seth Hillbrand wrote: > ​This fixes artifacts remaining on the screen when touchpad scrolling is > enabled. > https://bugs.launchpad.net/kicad/+bug/1735669 > > The attached

Re: [Kicad-developers] [PATCH 0/6] A few compatibility fixes

Simon, I merged your patches into the development branch. Thanks, Wayne On 12/05/2017 09:42 PM, Simon Richter wrote: > Hi, > > these are a few things that cause build errors on MSVC, where gcc accepts > invalid code. Most of them are obvious. > > The pcb_test_window executable needs to be

Re: [Kicad-developers] [PATCH] Fix artifacts on touchpad scroll (fixes lp:1735669)

Merge to get additional testing please. I can't compile source. On Wed, Dec 6, 2017 at 4:21 PM, Wayne Stambaugh wrote: > Has anyone else had a chance to test this or should I just merge it to > get additional testing? > > On 12/04/2017 07:45 PM, Seth Hillbrand wrote: > >

Re: [Kicad-developers] [PATCH] Fix artifacts on touchpad scroll (fixes lp:1735669)

Has anyone else had a chance to test this or should I just merge it to get additional testing? On 12/04/2017 07:45 PM, Seth Hillbrand wrote: > ​This fixes artifacts remaining on the screen when touchpad scrolling is > enabled. > https://bugs.launchpad.net/kicad/+bug/1735669 > > The attached

Re: [Kicad-developers] Python: time_t needs mapping; tentative patch

JP, Would you please test this patch when you get a chance? I took a quick look at it and it seems correct but I don't know when I will have time to test it. Thanks, Wayne On 12/05/2017 12:00 PM, Henner Zeller wrote: > Alright, here is a reworked patch that includes the ideas discussed here >

Re: [Kicad-developers] [PATCH 0/6] A few compatibility fixes

On 12/06/2017 06:42 PM, Chris Pavlina wrote: > On Wed, Dec 06, 2017 at 11:38:21PM +, Wayne Stambaugh wrote: >> Simon, >> >> I'm OK with most of these patches but since when is it invalid to >> initialize a c array in c++ (patch 4)? Isn't c a subset of c++ > > No, no it is not. OK,

Re: [Kicad-developers] [PATCH 0/6] A few compatibility fixes

Wayne- That was my mistake. C++ doesn't specify the C99 initialize by enum reference. So Simon is correct. -S On Wed, Dec 6, 2017 at 3:38 PM, Wayne Stambaugh wrote: > Simon, > > I'm OK with most of these patches but since when is it invalid to > initialize a c array in

Re: [Kicad-developers] [PATCH 0/6] A few compatibility fixes

On Wed, Dec 06, 2017 at 11:38:21PM +, Wayne Stambaugh wrote: > Simon, > > I'm OK with most of these patches but since when is it invalid to > initialize a c array in c++ (patch 4)? Isn't c a subset of c++ No, no it is not. > or is > this just a fix to get kicad to compile with msvc? If

Re: [Kicad-developers] [PATCH 0/6] A few compatibility fixes

Simon, I'm OK with most of these patches but since when is it invalid to initialize a c array in c++ (patch 4)? Isn't c a subset of c++ or is this just a fix to get kicad to compile with msvc? If it's the latter, the coding policy is pretty clear about that. Cheers, Wayne On 12/05/2017 09:42

Re: [Kicad-developers] Symbol library table remapping question

On 12/06/2017 06:21 PM, Bernhard Stegmaier wrote: > > >> On 7. Dec 2017, at 00:10, Wayne Stambaugh wrote: >>> >>> So, I guess this won’t match as you said, or do you attempt to resolve >>> the symlink for comparison? >> >> No, the correct remap is to use the same

Re: [Kicad-developers] Simulator towards 5.0

ccmake is only useful when you aren't interested in scripting builds. It is a decent tool to discover the options but I would much prefer cmake --show-options to having to open up a GUI app. On 12/06/2017 06:13 PM, Jacob Schmidt wrote: > I got frustrated a while back because people were talking

Re: [Kicad-developers] Symbol library table remapping question

> On 7. Dec 2017, at 00:10, Wayne Stambaugh wrote: >>> >> >> So, I guess this won’t match as you said, or do you attempt to resolve >> the symlink for comparison? > > No, the correct remap is to use the same library that was being used > prior to the remapping. I think

Re: [Kicad-developers] macOS GUI Quirks

On 12/06/2017 11:40 AM, Bernhard Stegmaier wrote: > Hi all, > > as some of might know, I am working on macOS and some things seem to work a > bit different there (wrt KiCad). > During my last project I came across some dialogs, widgets, etc. where > initial sizing is not correct (so, not all

Re: [Kicad-developers] Simulator towards 5.0

I got frustrated a while back because people were talking about the spice integration like it was a real thing, but I had never seen it. That lead me to google how to list cmake options, and I found ccmake. ccmake is a wrapper around cmake that was useful to me. Maybe it will be for someone

Re: [Kicad-developers] Symbol library table remapping question

On 12/06/2017 04:15 PM, Bernhard Stegmaier wrote: > Hi Wayne, > > Thanks for the explanation. > >> On 6. Dec 2017, at 21:47, Wayne Stambaugh > > wrote: >> >> This all depends on the symbol library list and symbol library path >> configuration

Re: [Kicad-developers] Symbol library table remapping question

Hi Wayne, Thanks for the explanation. > On 6. Dec 2017, at 21:47, Wayne Stambaugh wrote: > > This all depends on the symbol library list and symbol library path > configuration of the project being remapped. Here is how the remapping > works: > > Attempt to find the

Re: [Kicad-developers] Symbol library table remapping question

On 12/6/2017 3:11 PM, Bernhard Stegmaier wrote: > Hi Wayne, > > Well, just think of me as a dumb user… :) > First time that I updated to a version with sym-lib-table support (fresh from > git some hours ago). > And yes, I read the blog post. > Maybe I didn’t understand it… might be another

[Kicad-developers] Symbol library table remapping question

Hi Wayne, Well, just think of me as a dumb user… :) First time that I updated to a version with sym-lib-table support (fresh from git some hours ago). And yes, I read the blog post. Maybe I didn’t understand it… might be another story… :) I decided to create a global sym-lib-table with all my

Re: [Kicad-developers] macOS GUI Quirks

Le 06/12/2017 à 17:40, Bernhard Stegmaier a écrit : > Hi all, > > as some of might know, I am working on macOS and some things seem to work a > bit different there (wrt KiCad). > During my last project I came across some dialogs, widgets, etc. where > initial sizing is not correct (so, not all

Re: [Kicad-developers] [PATCH] Add double-click handling to disambiguation menu

Every once in a while, someone submits a fix for a bug that I didn't even remember existed, but that makes me want to hug them when it's fixed. On Wed, Dec 06, 2017 at 06:05:58PM +, Seth Hillbrand wrote: > ​The attached patch fixes https://bugs.launchpad.net/kicad/+bug/1154020 > > The

[Kicad-developers] [PATCH] Add double-click handling to disambiguation menu

​The attached patch fixes https://bugs.launchpad.net/kicad/+bug/1154020 The current double-click handler in draw_panel​ gets overridden by the disambiguation menu, preventing double-clicks from being properly handled. This patch introduces a delay between the mouse up and handling the

Re: [Kicad-developers] Signal integrity simulation within Kicad

Cool! I took a brief look at your code and looks like a good starting point although I have not compiled it. Unfortunately the legacy canvas cannot use the same draw call, as the architecture is completely different. To be honest, I would not worry about supporting the legacy canvas if I were you

Re: [Kicad-developers] Signal integrity simulation within Kicad

Hi Jon, thanks a lot for your help. On 12/05/2017 03:51 PM, Jon Evans wrote: > For (2), the PCB_BASE_FRAME methods are for the legacy canvas, so I > wouldn't worry about implementing your feature there if I were you, > since it will eventually be removed. > The RATSNEST_VIEWITEM is what is used

[Kicad-developers] macOS GUI Quirks

Hi all, as some of might know, I am working on macOS and some things seem to work a bit different there (wrt KiCad). During my last project I came across some dialogs, widgets, etc. where initial sizing is not correct (so, not all content is shown), etc. Mostly no real showstoppers, but leaves

Re: [Kicad-developers] Simulator towards 5.0

Are we not in feature freeze, the features that I enabled by default is from my understanding the ones that will be built into the official ones. And yes, the people that are compiling a non-standard install shuld be savvy enough to be change the compilation settings. That is why i think the

Re: [Kicad-developers] Zone filling

Hi Heikki, I might have not understood the question, would you please rephrase it? I assumed you are asking why your code has not been merged and Tom's has been accepted. Regards, Orson On 12/06/2017 11:45 AM, Heikki Pulkkinen wrote: > Hi Maciej > > You did not answer my question, and those

Re: [Kicad-developers] Simulator towards 5.0

On 12/5/2017 12:31 PM, Simon Richter wrote: > Hi, > > On 05.12.2017 17:30, Maciej Sumiński wrote: > >> When you build a program, do you always go through its build manual or >> do you start with 'cmake .. && make'? I think there is no point >> enforcing an optional dependency. Another good

Re: [Kicad-developers] [PATCH] Component table view initial columns sizing

Bernhard, I tested your patch on windows and linux and everything looked fine so I merged it into the development branch. Thanks, Wayne On 12/5/2017 3:37 PM, Bernhard Stegmaier wrote: > Wayne, > > No problem… never used it before, but always good to learn something new… :) > Attached. > > >

Re: [Kicad-developers] Simulator towards 5.0

Hi, On 06.12.2017 11:12, Kristoffer Ödmark wrote: > I do not see why anyone is even objecting to this? Where is the logic at > having a default build that does not correspond to any of the official > packages?! That usually happens because the nightly builds enable all the experimental features

Re: [Kicad-developers] Simulator towards 5.0

The subtle difference is your resolve wx dependency with 'apt-get install libwxgtk' and to get libngspice you need to cast a few spells when there is no package. On 12/05/2017 06:02 PM, Nick Østergaard wrote: > But it would also fail to build if you did not install wx. > > Den 5. dec. 2017 5.21

Re: [Kicad-developers] Zone filling

Hi Heikki, Your branch contains a lot of code that is not in the official repository and should not be merged (different connectivity algorithm, alternative way for via stitching interleaved with numerous #ifdef). There is no easy way to apply your changes to the master branch, as they have

Re: [Kicad-developers] Simulator towards 5.0

I sent the wrong patch before attached the correct now. Silently compiling something else then what was expected is much much worse than failing. I do not see why anyone is even objecting to this? Where is the logic at having a default build that does not correspond to any of the official

[Kicad-developers] Zone filling

Hi, I tested that new filling, and there is no improvement against with my parallel filling algo witch idea Tomasz copied. olinuxino A64,my 13s, new 12s. WRS, my 1min 43s, new 1min 44s. What is the meaning of rules? Regards Heikki ___ Mailing