I took a quick look at the DRC code, and it looks like it is doing an
exclusive check on the minimum distances for clearance -- i.e. it is
requiring the clearance be greater than the minimum, not greater or equal.
I'm not familiar enough with this part of the code to want to submit a
patch for this
Hi John,
I am mainly looking at eeschema right now, so I haven't studied the GAL
code closely yet. pcbnew's behavior in GAL canvas is certainly better than
legacy and eeschema, but still does some odd things that I want to look
at. I will have to get familiar with GAL in order to see how my chan
> On Feb 12, 2017, at 5:59 PM, Andy Peters wrote:
>
> I am using a nightly build from 26 January 2017 on a Mac.
>
> The design has a handful of differential pairs. I have set up design rules
> for most nets in the design as 1.6 mm trace width and 1.6 mm clearance. I
> created a net class for
On Mon, Feb 13, 2017 at 6:39 AM, Jon Evans wrote:
>
> The core of the issue is how KiCad thinks about selection of objects
> compared to most other software that deals with graphical objects that the
> user interacts with.
>
> Most applications have the concept of a "selection set" that contains 0
Hi Clemens, thanks for the suggestions! I will take some time to think
about them.
Hi Kristoffer, I understand there will be people like you who want the
current system, and I am trying to figure out the best way to propose
something that would be accepted by all. The current system has some
pro
> On 12 Feb 2017, at 22:18, Wayne Stambaugh wrote:
>
> On 2/12/2017 5:37 AM, Simon Wells wrote:
>> i am stuck on the below as i do not understand whats trying to be
>> achieved doing this
>>
>> # For phase 1, copy _pcbnew.kiface to the python module. line onward
>> (line 733ish)
>>
>> until th
On 2/12/2017 5:37 AM, Simon Wells wrote:
> i am stuck on the below as i do not understand whats trying to be
> achieved doing this
>
> # For phase 1, copy _pcbnew.kiface to the python module. line onward
> (line 733ish)
>
> until the end of the if, and its broken for me.
It should just be a cop
Please!!:
- Move .kiface into $PREFIX/lib on linux, and the equivalent place on
other systems
- Rename them from _foo.kiface to foo.so on linux and osx and foo.dll on
windows
- Stop installing them with the executable bit set on linux! Presumably
osx too. It's totally unnecessary for share
As the kifaces are just shared objects/libraries is there any reason
they must be named .kiface instead of .so (or other name used on
system for dynamic libs), It seems to just be making things more
difficult and confusing when people see .kiface and have no ideaa what
it means.
These should reall
Hi Fabrizio,
The changes are on the tip of this branch:
https://code.launchpad.net/~john-j-beard/kicad/+git/kicad/+ref/icons
I have deliberately tried not made drastic changes to the icons such
that they would be unrecognisable to users of older documentation,
it's mostly alignment and colour tw
As long as you don't start to rename all icons that should fairly painless
to update in the docs.
Den 12/02/2017 18.28 skrev "Fabrizio Tappero" :
> Hi John,
> these improved icons look great! thanks for the effort. I think this work
> should be included. Could you please submit a patch for this t
Hi John,
these improved icons look great! thanks for the effort. I think this work
should be included. Could you please submit a patch for this to Wayne or JP.
A lot of icons could be improved and as Wayne mentioned it is important to
kind of coordinate us so that we do not create great icons that
This patch fixes a problem with GAL where zones are ignored in ratsnest
calculation.
The problem is that calling RN_DATA::Update on a zone with no polygons (an
unfilled zone) will remove the zone successfully, but then RN_DATA::Add is a
no-op.
From this point on, because ::Update refuses to wo
On Sat, Feb 11, 2017 at 5:54 AM, Nick Østergaard wrote:
> While we are at it, what about making the line graphic icon such that
> it matches the style of the arc and circle? That is making it not
> dashed, and add anchor point indicators?
I think that the "Graphic Line" tool in pcbnew should act
This patch adds support to hide individual nets from ratsnest by adding an
extra tickbox to the 'List nets' dialog.
The ratsnest visibility is stored in NETINFO_ITEM, which I'm not sure is
the right place to put it. I tried using IsVisible/SetVisible from RN_NET,
but that doesn't work because
Hmm, I am a fan of the selection menu that pops up actually, I would
like to keep it.
I think that the list can be used simultaneous with the hotkeys and
autoselection. Just hide it whenever another action is invoked on the
item that is curently selected in the list.
- Kristoffer
On 2017-02
i am stuck on the below as i do not understand whats trying to be
achieved doing this
# For phase 1, copy _pcbnew.kiface to the python module. line onward
(line 733ish)
until the end of the if, and its broken for me.
also can we please formalize a policy in the CMakeLists.txt files that
do_th
17 matches
Mail list logo
