Not requiring DR/DRC is appreciated.
Netclasses don't work with my designs on a fundamental level and if
there were not a way I could ignore them, I would not be able to use
KiCAD. Likewise the new interactive router which spends most of its time
in Highlight Collisions mode with Allow DRC
Hi Seth,
I was thinking about a similar issue which is that we probably can’t require
users to move to the new DR system (as it will be considerably more technical).
So perhaps using the old system as defaults which can be overridden by the new
makes sense.
Cheers,
Jeff.
> On 4 Jul 2019,
Hi Jeff-
Ideally, I'd like to find an option that doesn't need to move twice
during v6. Toward that goal, what if we moved edge_clearance to the
defaults section? Until we implement the design rules and/or
polygon-specific clearance, it simply controls everything. Once we
integrate the
I agree that it shouldn’t be its own tool, but PCB_EDITOR_CONTROL is getting
too big.
Let’s just name this tool the PCB_INSPECTION_TOOL, and then I’ll move the
highlight and list nets stuff, and the DRC dialog to it later. That’ll nicely
parallel the EE_INSPECTION_TOOL.
Cheers,
Jeff.
> On 4
This looks nice, but a few comments from my initial usage of it:
Usability:
1) When I use english units, your statistics dialog gives the dimensions in
mils. It should probably give those in inches instead, since that is what
the grid panel at the bottom gives.
2) Including the board area would
Hi,
nice addition indeed...
You may find someone with the same
needs at the forum
https://forum.kicad.info/t/how-to-get-pin-count-and-board-size-for-assembly/17792
There is a small plugin offering this option ATM,
listing what Mario
is asking for...
It would be nice to have it in the
Based upon a bug in the tracker, it may be working or not working depending
upon external files, rather than exactly which nightly build it is.
On Wed, Jul 3, 2019, 8:16 AM Nick Østergaard wrote:
> Cool, thank you for verifying.
>
> ons. 3. jul. 2019 14.54 skrev Seth Hillbrand :
>
>> On
Looking through our current set of board setup properties, only
solder_mask_min_width would join edge_clearance in a design_rules section.
Most of the other properties are either most-recently-used values
(zone_clearance, via_size, etc.) or true DRC values (uvias_allowed, trace_min,
etc.).
All compilers need this in standards-compliant mode.
---
CMakeLists.txt | 4
1 file changed, 4 insertions(+)
diff --git a/CMakeLists.txt b/CMakeLists.txt
index ee43d9eb98..c73c86a291 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -245,6 +245,10 @@ if( WIN32 )
# define UNICODE
Defines:
- inhibit generation of #pragma comment(lib, ...) from boost
- inhibit warnings about "unsafe" containers
- inhibit warnings about "unsafe" C functions
- inhibit warnings about "deprecated" POSIX functions
- suppress min/max macros from windows.h
Flags:
- source and execution
---
pcbnew/pcb_edit_frame.h | 3 ++-
pcbnew/pcbnew_config.cpp | 12 ++--
2 files changed, 8 insertions(+), 7 deletions(-)
diff --git a/pcbnew/pcb_edit_frame.h b/pcbnew/pcb_edit_frame.h
index 705f5f7f4c..dadb6cba0e 100644
--- a/pcbnew/pcb_edit_frame.h
+++ b/pcbnew/pcb_edit_frame.h
@@
This uses the Windows native Fiber API.
---
common/system/libcontext.cpp | 66
include/system/libcontext.h | 16 ++-
include/tool/coroutine.h | 8 --
3 files changed, 87 insertions(+), 3 deletions(-)
diff --git
Windows headers assume min/max to be macros, but we set NOMINMAX to hide
the macro definitions. This pulls in an alternative implementation.
---
common/gal/cairo/cairo_print.cpp | 6 ++
1 file changed, 6 insertions(+)
diff --git a/common/gal/cairo/cairo_print.cpp
---
CMakeModules/FindOpenSSL.cmake | 342 -
1 file changed, 342 deletions(-)
delete mode 100644 CMakeModules/FindOpenSSL.cmake
diff --git a/CMakeModules/FindOpenSSL.cmake b/CMakeModules/FindOpenSSL.cmake
deleted file mode 100644
index
Hi,
another attempt at getting the MSVC patchset merged. :)
The mails with the patches are for commenting, this branch should probably
be merged from the "msvc" branch under https://git.launchpad.net/~sjr/kicad
in order to preserve author/date information properly.
Simon
Simon Richter (5):
---
eeschema/sim/ngspice.cpp | 1 +
1 file changed, 1 insertion(+)
diff --git a/eeschema/sim/ngspice.cpp b/eeschema/sim/ngspice.cpp
index fa1d3e3a97..4b173ef7af 100644
--- a/eeschema/sim/ngspice.cpp
+++ b/eeschema/sim/ngspice.cpp
@@ -28,6 +28,7 @@
#include "ngspice.h"
#include
---
include/lib_tree_item.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/lib_tree_item.h b/include/lib_tree_item.h
index 5ad5ef4bd8..28f69b7c03 100644
--- a/include/lib_tree_item.h
+++ b/include/lib_tree_item.h
@@ -27,7 +27,7 @@
#include
#include
-
On 2019-07-04 09:24, Jeff Young wrote:
Since this is DRC, can we keep it in its current place until the DRC
manager goes in
Well, there’s DRC and there’s DR. The other options really control
only what is *checked*, whereas this one controls stuff *on* the
board. Granted a lot of Jon’s rules
Hi SHuklin! ( is this the romanization of your name? :) )
This is just my user feedback:
That is a cool addition, another feature suggestions would be to list the
components by "Fabrication attributes" "Through hole"/"Surface mount"/"Virtual"
Each footprint has this attribute so I guess you can
> Since this is DRC, can we keep it in its current place until the DRC manager
> goes in
Well, there’s DRC and there’s DR. The other options really control only what
is *checked*, whereas this one controls stuff *on* the board. Granted a lot of
Jon’s rules will also fit into the DR camp, but
On 01/07/2019 23:49, Nick Østergaard wrote:
> Hello Tomasz
>
> Do you have any comments on the wxwidgets version?
Hi Nick,
I have 3.1.1 in my MSYS environment, probably manually built.
We have two options:
- ask MSYS folks to update wxWidgets in the package repository,
- factor out stack trace
Le 04/07/2019 à 11:28, Jeff Young a écrit :
> A general-purpose way to solve this occurred to me:
>
> 1) we’ve talked about having user-defined attributes on footprints — but
> they should really be on all items
> 2) then in Jon’s new DRC language we could define a clearance: * to
> *[@mousebite]
A general-purpose way to solve this occurred to me:
1) we’ve talked about having user-defined attributes on footprints — but they
should really be on all items
2) then in Jon’s new DRC language we could define a clearance: * to
*[@mousebite] (using XPath syntax ‘cause I can’t remember what
to 4. heinäk. 2019 klo 2.27 Jeff Young (j...@rokeby.ie) kirjoitti:
> Bug fix. Many of our customers consider the edge cuts having width to be
> a bug.
>
>
It's feels clumsy but it works. On the other hand I saw at least one
manufacture state that you should have only one width in edge outline
24 matches
Mail list logo
