Hi Jeff-
I just checked a couple of Eagle boards and the imports are now slightly
problematic. See the attached image. This corner is square in Eagle.
It can be very difficult to edit zones with a bunch of extra points, so
I'd like to avoid this if possible.
Best-
Seth
On 2019-07-15
Oops, sorry about that. Should read 5.1.3.
On 7/15/2019 12:50 PM, Steven A. Falco wrote:
> On 7/15/19 12:26 PM, Wayne Stambaugh wrote:
>> Were do we stand on the translations? I saw a few commits to the
>> translations repo over the past week but it didn't look like all
>> languages got
On 7/15/19 12:26 PM, Wayne Stambaugh wrote:
> Were do we stand on the translations? I saw a few commits to the
> translations repo over the past week but it didn't look like all
> languages got updated. Please let me know when the translations are
> ready so we can tag the source and library
Were do we stand on the translations? I saw a few commits to the
translations repo over the past week but it didn't look like all
languages got updated. Please let me know when the translations are
ready so we can tag the source and library repos. I have the release
announcement ready to go.
Remind me, is this feature still in a seperate branch to master, or
how is it enabled?
On Thu, 11 Jul 2019 at 21:08, Nick Østergaard wrote:
>
> @Tomasz Wlostowski I just found that it looks like someone has
> uploaded a wxwidgets 3.1 pkgbuild for the mingw-packages for msys2, I
> could try to
On 7/12/2019 8:46 AM, Simon Richter wrote:
> Hi,
>
> My layout would be
>
> m_footprintListBox->Bind( wxEVT_RIGHT_DOWN,
> [this]( wxMouseEvent& )
> {
> this->PopupMenu( this->m_footprintContextMenu );
> } );
I like the way this looks compared to the other
Ian,
I would prefer that we not mix event handling styles unless there is a
good reason such as dynamically binding/unbinding for adding temporary
event handling. For new code, I'm fine with either method with the
caveat that all of the Bind calls be defined in the same function rather
than
Hello there,
been using Kicad for a while and have not looked back at eagle except
for project imports.
However, I found all those vertical texts in eeschema quite disruptive.
So I've done something like in attached screen shot over the last couple
of days working off of master under Linux.
Hi,
we have a failing test, consistent on all tested platforms:
[Error] - check common.holeyPolySet.Collide( VECTOR2I( 11, 11 ), 5 ) has failed
== [File] -
/var/lib/jenkins/workspace/linux-kicad-head/src/qa/common/geometry/test_shape_poly_set_collision.cpp
== [Line] - 160
The first build[1]
Oh, good. Not sure how I missed where we set the min-width.
So our old algorithm will mimic Eagle irregardless of my change (MiterLimit
only comes into play when inflating, not when deflating).
However, the new algorithm would need my change to produce the same curves as
Eagle — but that puts
Hi JP,
The new algorithm produced very sharp points where the min-width setting
resulted in drop-outs. These would be prone to peeling. So I changed
Clipper’s MiterLimit to nicely chop them off (giving square ends, but with
angles above 90º). I then modified Clipper to round them off so
Le 14/07/2019 à 22:14, Jeff Young a écrit :
> Hi JP,
>
> Why were the non-stroked zones implemented? Is it entirely for performance?
>
> Is the plan to make them default in 6.0?
>
> Thanks,
> Jeff.
It is mainly to fix an issue for very large boards: stroked filled
polygons generate a lot of
12 matches
Mail list logo
