So how long have you been using KiCad? 20 minutes?
With “impossibly slow” do you mean a keypress and a mouse click? I get so annoyed by your many complaints that it’s hard to even read/comprehend your whole post.
Yes, and that’s a feature of KiCad. KiCad’s interactive router being able to shove things aside to make room for other things is a quite powerful and very nice feature. But it does need some time and effort to get used to.
I apologize if my approach is a little brusk. I’ll try to edit out my unecessary comments in the post. I’m in between trying to figure out it the behavior is normal and I just don’t know how to use it right, or if it’s a bug. The V key was not switching layers for me. I got the top and bottom layers paired before I wrote it up but I didn’t pair the inner layers until recently. Originally I thought the top and bottom paired automatically. Perhaps I also needed pair the inner layer too, and then disable them? Was this what now allows me to reliably switch layers? So the layer switching is OK for me now. Thanks for the replies. I’m just trying to figure this out.
But I’m still not sure why the vias don’t move when I hit D or G. They unselect themselves when I hit the key. For instance. The below selection I could grab with the vias and then drag with a mouse click or M, but the traces disconnect. When I tried it with D or G, the vias the traces connected to the vias unselected them selves. I was trying to moving everything with its vias and traces closer to the CPU
KiCad’s interactive router being able to shove things aside to make room for other things
To be clear Push And Shove is just one of the modes in the router and when you don’t want to shove existing things around, you can use “walkaround” or “highlight collisions” mode. There is a slot for a hotkey for each, as well as a hotkey slot for cycling the mode.
There is a difference between Move and Drag. Moving just moves items (footprint or a selection) It does not maintain any sort of connectivity
You’re also mixing up several things in one block of text (which is something that easily confuses me).
If you have a via placed, you can click on it, and then drag it around with the mouse (no key whatever needed). and it will keep the tracks attached.
If you click on a footprint, and then “drag” it around, then KiCad defaults to the “move” function, and it gets detached from the tracks.
If you hover over a footprint (no need to select it first) and then press d for drag, then KiCad drags the footprint, and it keeps tracks attached. KiCad won’t accept an end position that violates DRC, but you can overrule this by keeping the [Ctrl] key depressed while finishing the drag. And similar for blocks. Creating a selection, then d drags the block around while keeping tracks attached.
Earlier you mentioned that:
… did not work for you. Does it work now?
I am not so familiar with the layer pairing. I have not designed a PCB with more then 2 layers yet myself.
The V function does seem to work for me now. It seems I need to hit V again to switch layers (now that I have all layers paired properly) which I thought would happen the first time I hit V. I’m also able to work by just selecting the new layer (similar to my old way of working in Eagle.) So it seems more workable to me now, but not entirely as expected.
I was unaware that drag worked differently whether it was hovering over a component vs one that was selected
At least there is progress.
And KiCad is “different” from eagle. This will take some time to get used to.
In 2021 Rene Poschl wrote a FAQ article about some differences between eagle and KiCad, but I don’t know how relevant that article still is.
Not really different, but without selecting, you can just drag one item. If you make a selection first, the whole selection gets dragged.
Just practice a bit and give it some time. You will probably get used to it pretty quickly. After a while you’ll start forgetting how that other program worked 
You can modify hotkeys in: … / Preferences / Preferences / Hotkeys
There are many hotkey options that do not have a default key assigned, but not for extra dragging options. You can drag a block (with whatever is in it at that moment). There is a significant difference between between dragging the mouse cursor from left to right, or right to left when you create the block. (Left to Right does not include the items that cross the block boundaries)
For the rest, maybe you are struggling with the Selection Filter in the lower right corner. With it you can set the object types which are selectable.
It’s OK. I’ll read up more on the manual and the modes. It’s more in-depth than the tutorials. Finding my way. It’s actually going faster than my adjustment to Eagle was once.
Considering moving to KiCad I have read all manuals before I downloaded KiCad V4 itself.
I read manuals and talked to folks before making the change, but info doesn’t stick until you put it into practice. Seeing that things are case-sensitive is another thing that tripped me up. Creating with a large complex schematic and placement before ever having laid a trace in KiCAD other than in a short simple tutorial. . . it’s trial by fire here. But all good
That’s true. My task was to find if KiCad is enough good to move to it from Protel 3. I am not doing huge designs and am not using all program possibilities so I had in mind just options I use and trying to find in manuals if they are in KiCad. My conclusion was that KiCad (V4 those time) has a few flaws compared to Protel 3 but had one important advantage - manual route with pushing other tracks. That decided. As V5 was expected soon I spend time waiting for it on defining my symbols and footprints and started first design with V5. V5 solved via-stitching problem. Both in KiCad V4 and my Protel 3 all GND vias you had to connect with tracks. Since V5 - you need not.
With each new main version I find some features that are helpful for me. Unfortunately V9 cut me off. To move to V9 I have to modify all my 300 footprints. I have heard that if I ask AI I should get the Python script to do what I want with my footprints, but I don’t know when I will find time to try to do it.
I don’t even know how to run a Python script, but it is probably the simplest part of this job
When I evaluated KiCad, it was still on the “Bazaar” version numbers (< V4) and a big factor in adopting it was that I saw there was quite some development going on. That gave me some insurance that the big flaws (back then library management was completely broken) would be fixed in due time. And I was right about that
Changing ECAD packages is like a new pair of shoes. They aren’t nearly as comfortable as the old pair was, but everyday you wear them they’ll get more . . . comfortable.
No, not really for me.
My immediate reason for a new EDA Suite was my switch from Windoze to Linux, but by that time the program I used (ultiboard 5.72) was so old and deprecated that it was high time to replace it anyway.
BTW I figured out my biggest problem. REVERSE THE ORDER OF “V” AND CLICK! It’s habit! For 30 years in both programs I’ve used I’ve placed the point where I want my via first with a click, then changed sides or placed the via with a command or hotkey. With KiCAD I hit the V first, THEN place the location with the click. If I click first then V with KiCAD it places the via, but it does not change side until I hit V a second time. It took me WAY TO LONG to figure this out. I knew this intellectually and could start working fine, but my fingers brain kept reverting. I thought it was some inconsistent bug. It’s my brain!
I never quite figured out why sometimes vias don’t drag with my other components near my MCU. But in all other cases I’m able to drag them with traces and components. At least I can still drag those vias independently to fix it and now that I’ve been using drag more I realize that there are good visual indications to confirm that it’s “dragging” and not just “moving”.
Can you update the title to something more appropriate. This topic has nothing to do with “Routing in KiCad being slow”. This throws people off cue who are later searching this forum.
The schematic uses Move and Grab for this. Why the difference? I never discovered Drag, and thought the PCB just didn’t have the Grab function at all.
A lot of key mapping between the schematic and PCB editors is very similar, but they are not the same. When I started to use KiCad I was a little bit annoyed that you start a Wire with w in the schematic, and start a track with x in the PCB editor.
And I do advise to set some time apart every now and then to do things like reading the manual or experimenting with menu options that you are not familiar with. Reading though the hotkey list (in which many keys can be assigned, but have no default key combo) also helps to get to know KiCad better.
I have read about them before I have even installed KiCad for the first time. But years passed till I discovered P hotkey in PCB editor that is very useful when I start new PCB.
