Electronics > KiCad

Why is KiCad PCB layout still clunky

(1/6) > >>

steaky1212:
Not to put KiCad down, but why is is that the PCB aspect still so clunky, especially with regards to moving components around.
- The default (and unchangeable) behaviour is moving components, instead of dragging them.
- Rotation components breaks the connection to the trace.
- I can't drag and rotate at the same time.
- If I drag a component, the traces default to collision mode.

And it doesn't look like any of these are being raised as issues on github. So weird

ataradov:
It is a matter of preference. I personally like the way KiCad implements PCB editing.

So, if anything the argument would be to add options for other types of behavior. But if they are not being added or even discussed a lot, people must feel that the default behavior is fine.

janoc:
And what would you expect to happen?

Given that KiCAD has online DRC, would you prefer:

- DRC constraints get violated, tracks touch/cross/short after you have rotated the part

- Tracks get automatically rerouted, possibly messing up a large part of the layout

There are no sensible options here unless you expect the software to read your mind.


Moving is the default only if you use the mouse. Use a hotkey if you want to initiate a drag. Much faster anyway.


--- Quote from: steaky1212 on August 12, 2024, 02:28:50 pm ---And it doesn't look like any of these are being raised as issues on github. So weird

--- End quote ---

Maybe because those are not really a problem for anyone?  You can change the behavior of the push-and-shove router (whether the tracks should collide or to reroute automatically) and dragging/moving is easily done by hotkeys.

ebastler:
Dragging parts (and dragging connected traces along with them) already is a supported operation. But frankly, it feels more limited than it needs to be. Drag mode gives up far too easily -- highlighting a trace overlap and throwing up its arms in despair. In many cases, a bit of local push & shove-routing would go a long way when dragging a part by a short distance, e.g. to make room for another component next to it.

No mind reading required, and it could make life much easier than the status quo, where I have to resort to moving the part, manually ripping up and re-routing many short traces. Always in danger of leaving some redundant trace segments behind, or having made some undesired connections during the component move.

So yes, I would wish for smarter component dragging, and I think it should be achievable.

nctnico:

--- Quote from: ebastler on August 12, 2024, 09:03:39 pm ---Dragging parts (and dragging connected traces along with them) already is a supported operation. But frankly, it feels more limited than it needs to be. Drag mode gives up far too easily -- highlighting a trace overlap and throwing up its arms in despair. In many cases, a bit of local push & shove-routing would go a long way when dragging a part by a short distance, e.g. to make room for another component next to it.

No mind reading required, and it could make life much easier than the status quo, where I have to resort to moving the part, manually ripping up and re-routing many short traces. Always in danger of leaving some redundant trace segments behind, or having made some undesired connections during the component move.

So yes, I would wish for smarter component dragging, and I think it should be achievable.

--- End quote ---
Just out of interest: Is there no way to just have the traces overlap (causing a DRC) and clean-up later by moving the traces around? I did watch a short video but that didn't answer this question.

Navigation

[0] Message Index

[#] Next page