My answer is: Always. That is because I only flip / rotate the part when I want it to. flip / rotate.
Exactly because it is so very easy to attach / detach wires from components makes a lot of editing of schematics simple, intuitive and straigtforward.
If you can’t keep your hands of the keyboard you can re-assign the “x” shortcut to [ctrl+alt+delete+x] or disable the shortcut so you can only flip / rotate with mouseclicks from a menu.
It depends on how you move the wire. If you move wires without moving the labels, then the labels simply stay where they are. if you block move wires you can easily choose if you also want to move the wires with the block or not.
@nickw:
I’m getting confused here It seems you are telling a a bunch of contradictory things. then “Forget the original post.” You say: “extra clutter” which I deem “essential information”.
All the slanted lines if you move a single component diagonally will detach the labels (Unless the attachment point of the labels is exactly on the endpoint of the wire! Have you tried that?).
But I can not believe you want all those slanted wires in your schematic anyway.
So simply do not move your components in this way (Or undo with [Ctrl+Z] if you did by accident).
"g"rab of a single component is only usefull for straight horizontal or vertical movements.
I have not gotten a single word of feedback about the block move, which can easily avoid most part of your “problems” with detached labels. It really seems to me that you sould experiment more with the multiple ways you can create and move / copy blocks.
You seem fixed on the single idea of having invisible wire labels which stay fixed on the wire.
I hope this feature never makes it into KiCad. I want to be able to see my wire labels. Everywhere! Always!
It’s simple and effective.
These invisible wire labels are also incompatible with KiCad. It is now very easy to copy a whole bunch of wires from the address bus of your SDram to the Databus of the SDram. If invisible wire labels are copied implicitly with it then that opens up a bunch of cans with wormholes.
The simplicity with wich it works now is one of the charms of KiCad.
I like it very much that you can "m"ove a component to a bunch of loose wires and then "g"rab the component and drag / stretch the wire endpoints along.
I do not see why these “invisible wire labels” would make anything
I also get 0.0 feedback about the library of writing the schematic in code instead of with KiCad, which might wel be worth it for you. You can generate your netlists from simple text files, which seem to me a good alternative for schematics which mosty consist of big data & address busses. But you probably have not even condidered this for >2s. The project seems to be SKiDL: https://forum.kicad.info/t/skidl-a-python-based-schematic-design-language/3743/4
When re-reading your posts I found this argument:
This is a bad idea. Having to click hundreds of wires one by one just to be able to see their net names and check if the net name is still compatible with the pin that the wire is connected to is a tedious job.
It is simply not compatibley with the easy and intuitive way you can move wires and components around in KiCad.
In my opinion the KiCad design team is doing an excellent job in making great software and this whole “problem” is so trivial that it is not worth much development effort.
I think that we can agree that we disagree here, and I think I am done with this conversation.