Ignoring the bovine references and attempting to answer the question:
Topological routing means using the connectivity graph of the system to
generate geometrical constraints, and also to generate specific geometry
for say traces or polygons. It's called that because it uses concepts
from the disc
On 02.12.19 21:37, Tomasz Wlostowski wrote:
> All of this is true - for autorouters. This whole thread started with
> Altium's videos about the improvements to their interactive
> (semi-manual) router. P&S actually use very few strictly topological
> concepts (in the case of Kicad P&S, mainly in t
On 02.12.19 22:25, Tomasz Wlostowski wrote:
> On 02/12/2019 21:51, Kliment (Future Bits) wrote:
>> The video looks very much like to me like the trace is following a
>> voronoi cell boundary with cells coming out from each obstacle outline
>> vertex. But what do I know? May
Hey,
Without prejudice to whether or not this should be in Kicad, and how it
should be implemented, there's a way to do this now, with existing
tools. You start from gerbers - libgerbv supports this operation out of
the box for example, and it knows exactly what it's trying to produce.
So you can
Hey,
Not sure who runs forum.kicad.info but the COMODO cert that was used for
it expired today. Most browsers will refuse to load it. Just wanted to
make sure whoever runs that server is aware. kicad.info itself (without
forum.) does not present a certificate at all.
Kliment
Actually ladybugs are murderous predators that kill lots and lots of
bugs - a single ladybug can murder thousands of aphids in a day. Spiders
are very inefficient by comparison. But that's going offtopic in an
already offtopic discussion.
Kliment
On 17.07.20 13:18, Mark Roszko wrote:
> You would
Having just routed a board with 56 diffpairs I have an idea about number 4:
I think we should treat diffpairs as single traces when routing and when
using the pns functionality to move them around. The trace should have
the thickness of 2x dpair trace width + 1x dpair trace gap, and have a
clearan
t; I want to write a script or piece of code to change diffpair width or gap,
>>> what idea should I use?
>>> I think about finding all coupled lengths of some differential pair and
>>> changing the gap on all of coupled lengths and don't touch it if it is
>>
I'd find it a loss if the scaling options were gone - I often end up
using scaling for things like inductors, where there's too much variety
to make a model for each size and height, so I'll often grab a model
with the correct fp and wrong height and scale it.
Kliment
On 29.09.20 19:38, Ian McIne
Another application I use has eye (oval outline, circular pupil, no
eyelashes) for visible and eye outline (no pupil) with crossout line
diagonally across it for not visible. Works pretty well.
On 14.10.20 17:07, Jon Evans wrote:
> (The contrast for the current icons is worse on Windows than on ot
Hi Markus. You need to make a fork under your own name, and then you can
make all the branches you like. When you're ready, you can then send a
merge request to the main kicad repository. Be aware that we are
currently in feature freeze so no new features will be merged before the
next release.
Kl
On 02.03.2018 06:52, Andrey Kuznetsov wrote:
> Thank you to someone on the dev team I guess for getting rid of the mouse
> warp events from right click, however the zoom mouse warp to the center of
> the screen is still a major WTF.
That is an option in preferences -> general -> pan and zoom
Global spread and place?
On 07.03.2018 23:20, Jon Evans wrote:
> Hi all,
>
> As part of preparing a new 6.0 roadmap, I want to make sure we have all
> functionality that only exists in Legacy mode captured on Launchpad so
> we don't forget about it. José just reminded me that Legacy mode in
> Pc
The best solution I've seen so far is the one that OpenCV implemented.
It's well described at
https://docs.opencv.org/master/da/d49/tutorial_py_bindings_basics.html
On 10.03.2018 21:44, Vesa Solonen wrote:
> Jon Evans kirjoitti 10/03/18 klo 15:57:
>
>> I'm interested in helping brainstorm this m
Hey,
I'm working with a part that has a very large number of
non-interchangeable units, each with many pins. For a part like this,
it's very difficult to tell which unit is which from the preview. Parts
have a description field that is shown in the list, but units don't. For
parts with non-interch
changes) on the current file format. I will add a unit description
> field for units in the new file format this way you can add a unique
> description for each unit should you desire.
>
> Cheers,
>
> Wayne
>
> On 3/22/19 4:38 AM, Kliment (Future Bits) wrote:
&g
yet - for the moment you have to add them as
normal fields. Patch is attached. All feedback very welcome.
Kliment
On 22.03.19 21:56, Kliment (Future Bits) wrote:
> I don't quite follow - what I'm proposing doesn't require any file
> format changes, I was planning to just u
ers,
>
> Wayne
>
> On 3/23/2019 7:34 PM, Kliment (Future Bits) wrote:
>> I have a prototype implementation of this now - descriptions are
>> currently taken from fields _UNITDESC_A, _UNITDESC_B etc. The unit
>> descriptions show up when browsing parts in the add dialog
One issue I can think of offhand is that searching for "R2" would find
"R21" and searching for "1uF" would match "0.1uF", both of which would
be annoying. Maybe an "allow partial matches" checkbox?
On 26.07.19 20:39, Jeff Young wrote:
> PCBNew’s current Find does a match against the whole string.
19 matches
Mail list logo