polygons in the board editor
>I am old enough to have used autocad 30 years ago and I can say with
>absolute certainty that trying to layout a board with autocad now or
>then is folly. Comparing a 2D drawing program with a board layout
>program is not helpful
>
I wish the developpers can
I can add the rc3 tag to the library repos sometime Sunday afternoon.
(central European time)
A few minor corrections would still be nice to get into v5 but we do not
have any deal-breaker that would merit postponing v5 from our side.
On 23/06/18 17:15, Wayne Stambaugh wrote:
Let's try to get
Attached
On 24/06/18 02:46, Wayne Stambaugh wrote:
Hey hauptmech
For the most part I'm fine with these changes. I think that the first
two paragraphs (sentences) in the "Schematic Symbol Libraries" section
of the version upgrade document could be merged into a single paragraph
since they are
Hi,
Is there anything in the schematic rescue or parsing code to handle the
change in valid characters (removal of ':' and '/')?
An internal translation when reading a pre v5 symbol or library that
translates all ':' to '' and '/' to '', would save the few
miserable people who will get
This patch looks good to me. I tried it and it looks better than without
on my machines.
-S
Am Sa., 23. Juni 2018 um 11:44 Uhr schrieb Maciej Suminski <
maciej.sumin...@cern.ch>:
> +1 for the patch. The change seems sensible just by looking at the raw
> diff and the presented images justify
Andrzej-
I would prefer that this be fixed when reading the malformed file, not
displaying. We fix it there, the display issue goes away. This also
protects from unintended side effects rather than trying to code work
arounds for a malformed board in multiple parts of the code.
-S
Am Sa.,
When you generate gerbers from a valid NPTH pad with hole size = pad
size, there will be no shape plotted on copper layers, so in my opinion,
this pad does not exist on copper layers. But this is more philosophical
discussion :)
Regarding clearance for router, you could just take the merged
+1 for the patch. The change seems sensible just by looking at the raw
diff and the presented images justify correctness.
Cheers,
Orson
On 06/23/2018 05:32 PM, Andrzej Wolski wrote:
> Wayne,
>
> this is after patch:
> https://imgur.com/a/54ESCMD
>
> Andrzej
>
> W dniu 2018-06-23 o 16:54,
This sounds great.
I should be able to make an RC3 build on Monday. The remaining V5
issues on the macOS packaging are mostly things like "Reword the
readme" and "update the background"! Finally! :)
Adam
On Sat, Jun 23, 2018 at 10:15 AM Wayne Stambaugh wrote:
>
> Let's try to get rc3 by
Looks very good to me. I could nitpick aesthetics (I think it might be a
_little_ bit too long now) but that's just useless bikeshedding - it's
very clear and visible and balanced.
On Sat, Jun 23, 2018 at 12:00:04PM -0400, Wayne Stambaugh wrote:
> This looks correct to me. Is there something I'm
This looks correct to me. Is there something I'm missing here? I don't
pretend to be an expert on character rendering.
On 06/23/2018 11:32 AM, Andrzej Wolski wrote:
Wayne,
this is after patch:
https://imgur.com/a/54ESCMD
Andrzej
W dniu 2018-06-23 o 16:54, Wayne Stambaugh pisze:
Andrzej,
Wayne,
this is after patch:
https://imgur.com/a/54ESCMD
Andrzej
W dniu 2018-06-23 o 16:54, Wayne Stambaugh pisze:
Andrzej,
Do you have an image of the same characters after you patch? The other
question I have is what happens when consecutive characters have and
overbar? AFAIK, the overbar
Hi JC,
On 06/22/2018 12:22 AM, jc wrote:
> I would like to explode an intersect, like 2 lines,if crossed, turn into 4.
We need more information. What intersecting lines are you talking
about? Wires in the schematic editor or traces, zones, or polygons in
the board editor? Also, why do you
Let's try to get rc3 by tomorrow. That will give us almost a week of
testing before the 30th. If no major issues arise between now and then,
I will tag 5.0.0 on the 30th. I will be traveling for vacation the
following week so this will give everyone time to get everything ready
for the stable 5
Andrzej,
Do you have an image of the same characters after you patch? The other
question I have is what happens when consecutive characters have and
overbar? AFAIK, the overbar should be continuous (no breaks between
characters). Did you test this as well. If this needs fixed, I would
like to
Hey hauptmech
For the most part I'm fine with these changes. I think that the first
two paragraphs (sentences) in the "Schematic Symbol Libraries" section
of the version upgrade document could be merged into a single paragraph
since they are related.
If no one else objects to these changes,
Is this malformed pad actually caused by KiCad or is it possible this
was cause by a script or manual editing? If it was caused by KiCad then
we need to figure out how this was allowed to happen and fix it.
Wayne
On 06/23/2018 02:54 AM, jp charras wrote:
> Le 22/06/2018 à 21:54, Andrzej Wolski
As I have said earlier, I have written a document about KiCad and
environment variables. It ended up being larger than I expected. It handles
even some tangential subjects and my style is verbose. Still I hope it
could be useful. I need feedback. Facts are of course the most important,
but I also
I am looking at this
https://www.boost.org/doc/libs/1_53_0/libs/geometry/doc/html/geometry/reference/algorithms/intersection.html
Will try it sometime.
在 2018-06-22 19:21:46，"Greg Smith" 写道：
Have a look at Python or KiCommand plugin. Also, consider asking this question
on KiCad user
Le 22/06/2018 à 21:54, Andrzej Wolski a écrit :
> No, this IS an error in the board :)
> If you open pad properties and click OK, it won't let you save it as is, you
> will have to enable
> copper layers.
> NPTH pads also HAVE TO exists on copper layers (I don't understand why, but
> they do).
20 matches
Mail list logo
