On 2019-07-06 17:16, Steven A. Falco wrote:
I am trying to import an Adafruit Eagle project into KiCAD 6 (built
from the current tip of the tree).
I placed a copy of the Eagle files and the conversion here:
https://www.dropbox.com/sh/6d5bqhsvwmjvta0/AACFjeWxfUAb73uTdmt5wNHNa?dl=0
The
I am trying to import an Adafruit Eagle project into KiCAD 6 (built from the
current tip of the tree).
I placed a copy of the Eagle files and the conversion here:
https://www.dropbox.com/sh/6d5bqhsvwmjvta0/AACFjeWxfUAb73uTdmt5wNHNa?dl=0
The schematic looks pretty good, but there seems to be a
Tom,
Not to pile on the questions, but does the linux stack trace support exist
in the entire 3.0.x line, or how far back does it go? Currently, the
minimum version searched by cmake is 3.0.0, and some major linux distros
only have 3.0.2 (Debian Stable, EPEL6/7, and Ubuntu 16.04 to name a few).
On 06/07/2019 09:04, Carsten Schoenert wrote:
> Hi,
>
> Am 05.07.19 um 23:28 schrieb Ian McInerney:
>> 3.1.x is essentially only available on the lesser-known distros and as
>> additional packages for OpenSUSE. Aside from that, most distros run
>> anything between 3.0.2 and 3.0.4. (see
>> here:
OK, not really. More of an “exercise left to the reader”.
I'm working through a bug that doesn’t reproduce on OSX, and so have been
leaning on others (JP so far) to do a bit of sleuthing. One side-effect is that
there is a lot of info in the bug report for people who aren’t familiar with
the
On 2019-07-06 10:17, Dave Vandenbout wrote:
Fixes: lp:1803623
* https://bugs.launchpad.net/kicad/+bug/1803623
---
pcbnew/swig/board.i | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
Looks good. Thanks Dave! Tests out on Python2 and Python3.
For my reference, why did you
Fixes: lp:1803623
* https://bugs.launchpad.net/kicad/+bug/1803623
---
pcbnew/swig/board.i | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/pcbnew/swig/board.i b/pcbnew/swig/board.i
index 91c41cc90..3bdc1e610 100644
--- a/pcbnew/swig/board.i
+++ b/pcbnew/swig/board.i
@@
I played with this a bit and I think we might want to reconsider.
The primary issue is that the point editor has a natural batching of
operations: you select the zone, move a bunch of points around, and then
deselect it. We re-fill on deselect.
Moving items that overlap a zone has no such
Hi,
Am 05.07.19 um 23:28 schrieb Ian McInerney:
> 3.1.x is essentially only available on the lesser-known distros and as
> additional packages for OpenSUSE. Aside from that, most distros run
> anything between 3.0.2 and 3.0.4. (see
> here: https://repology.org/project/wxwidgets/versions).
well,
9 matches
Mail list logo