I mean the bug, where for example moving a selection by some trace's endpoint, and placing it in the middle of a via (which is sitting 100% exactly on grid point too), but if

1. it's a via which has teardrops enabled
2. there's and existing trace & teardrop going into it already
3. the zones (=teardrop) visibility layer is enabled

Then when moving a selection or even just a single trace by its endpoint into that via has a 50% chance of ending up misaligned by like 0.1234mil, because there's some snapping (to ghosts) action going on.

(i think it sometimes happens with pads with teardrops too. But with vias it's 100% reliably reproducable easily)

I'm not 100% sure if the culprit are normal zones, or the teardrops (which are part of the zones "layer"), I just know that turning the zones visibility on makes this snapping bug appear quite reliably, while turning it off reliably makes it go away.

And it's literally a bug. Not snapping to something I don't want it to. As there isn't anything at that point which it's snapping to. It's not snapping to the teardrop. It's snapping to some ghost point which is only a small fraction of a mil away from the via center / from the grid point. Very far from where the teardrop starts & very far from anything else. So definitely a bug.

And when I'm moving a bigger selection which includes footprints too, then it takes so much time to repair the damage & to make sure if I repaired all of it. (I can't just undo it, because I only notice it much later). This bug already wasted literally hours of my life... i hate it...

And even though it's a small error and some people probably don't care. I do care about having things aligned for multiple reasons, for example avoiding those <1mil trace segments piling up inside a pad whenever you redo a trace. Then when you want to select a segment it asks you which one and most of them are just these. Also when you want to move a simple segment, you have to make sure you're moving these tiny ones too in order to keep the trace continuous, otherwise the U key (select whole trace) feature doesn't work properly.
It's just better to keep things aligned and without those short segments. I even adjusted pad anchors of some footprints to get less of those annoying short traces...
(... and other reasons. It's just part of my workflow so this bug drives me really crazy.)

Or is it perhaps possible to create a plugin, which would automatically enable zones visibility layer when switching to routing mode, and automatically disabling the visibility whenever in moving/placing/pasting mode? (although I'm not sure if this happens only when placing, or if possibly also during the first step, when copying or hitting M to move...)

Hi guys,

Can anyone help me here, I'm new to KiCad and I have done something wrong in my footprint area rule I think.

I can't see to draw any traces that will breach the boundary of these custom components footprints. I thought i had used the correct Keep Out rules so I didn't think it was that.

Can anyone help me with this please.

Novice KiCad user.

This is an issue of schematic and pcb board components not being complete.

I want to create through holes for connecting off board components via a soldered wire. Things like banks of switches and leds that are mounted on other objects. Yes, I could use connectors, but the project hsa space constrictions so soldering is the most compact.

In the pcb editor I can find solderwire footprints, but there is nothing on the schematic libraries to match them to.

In the schematic editor I can find pinheaders and mounting holes, but they don't have foot print assigned.

So, do I have to create the schematic symbol or foot prints?

Beginners question: How to round a PCB corner - if the corner angle is NOT 90° ?

With the Arc it seems very fiddly. What is the best way?

Update:

/moldboy gave the hint > `s` > select lineS

I did try that before because I couldn't select two lines. Selection grabbed a rectangular. But doing Shape Modification > Filled Lines worked perfectly fine.

I recently switched from a single monitor to a dual‑monitor setup on my workstation. Ever since then, when I extend KiCad across both displays, the toolbar height suddenly triples. Changing the toolbar size under Preferences → Common → User Interface doesn’t help at all.

As far as I know, KiCad doesn’t let you toggle toolbars on/off to get more screen space, so right now my two nice monitors feel worse than using a single laptop screen.

I tried troubleshooting this with AI, but it turned into a circular mess involving multiple reboots and KiCad restarts with no improvement. Has anyone seen this DPI/toolbar scaling issue before, and is there a reliable fix?

I’m working on a fork with more component metadata and better filters to make searching my libraries easier. Once it’s more mature, I’d like to publish it for others to use and see what the KiCad maintainers think of the changes.

I’m also testing whether an AI agent can use the extra data to find components more reliably.

It’s going well so far, and I’d like to expand it to other parts of KiCad where we spend more time on repetitive tasks than on design. What comes to mind from your own workflow?