when I try to drag a track there is always an interaction with the rest of them, it’s like the set of the interactive routing is always on ‘Shove’ but for dragging it cannot be changed to ‘Walkaround’, if I change it to ‘Highlight collisions’ it works. It’s that normal or there is some other setting for it?
I don’t quite understand, you seem to be aware of the settings and say “it works” in certain mode. Then you ask if there is some other setting for it. What do you mean?
It works as it should in ‘Shove’ and in ‘Highlight collisions’, but for my understanding of the how it should be, it doesn’t in ‘Walk around’ mode, in this mode the dragging behaves the same than in ‘Shove’, I’m asking if somebody else has the same problem (then this may be a bug), or if should I do some combination of other settings to achieve the ‘correct’ behavior of the 'Walk around’ mode.
Just to be clear, every mode works fine when I’m drawing the tracks, but we are talking about dragging them.
I think this is normal behavior. The walk around algorithm simply might not be able to walk around if both of its ends are tied to an endpoint already. This would explain why it behaves this way. (This is a conjecture. I do not really know if there even is a technical reason or if it simply was a design decision.)
Make a wishlist bug report over at the bugtracker and request your feature. Give a good explanation of what problem you expect this feature to solve. (A usecase)
You are in the F11 mode. If you want a more manual approach, goto the F9 Legacy mode and try dragging/moving the track of interest. Sometimes I feel like the magic features in Modern F11 try too hard for what I had in mind.
I just make a short video to illustrate how both modes behave the same, I just think in Walk around the via should not move the other things around, if it cannot be moved, it should remain where it is.
But even when they seem to behave the same, there is a different ‘feeling’ of the movement when it is in Walk around mode, and the processor load is bigger.
The "walk around’ wording to me implies it applies to track routing, whilst in that test, you are picking and moving a via.
Did you try routing a trace, to see how "walk around’ changes when applied to tracks ?
It may be the designers of KiCad never thought to test via-move ?
Do you want to move a via, but with Shove-off and DRC-prevent on ?
Highlight collisions does not shove tracks, but it has a slightly lower IQ than it could have, in that it visually warns but does not prevent an illegal release, so it cannot lazily ‘pack’ items.
Users must select a fine grid, and then watch/move very carefully.
Walk-around seems rather similar to Shove, and there could be scope for a middle ground option ?
ie an option that prevents collisions, and does allow lazy packing of items, without shove.
Sometimes Shove is too large a hammer, and Highlight collisions is too dumb a hammer…, be nice to have another tool in the tool-belt here
It seems more difficult to explain than I thought at the beginning of the thread
Did you try routing a trace, to see how "walk around’ changes when applied to tracks ?
Yes, it is stated over there, in the third post, when I’m routing all the options behave as it can be understood when one read the name of it (intuitively).
I just think ‘Walk around’ should not ‘Shove’, it should only walk around, either when one is routing or when is moving an object (this case a via, but it can be a track, sadly seems like the footprints cannot be dragged yet).
Yes, that is how it actually tests on my somewhat older V5. I can release either a dragged Via, or trace, with the warning colouring active, and it allows the violating release, no matter what ‘allow DRC violations’ setting.
Yes, it seems the ‘Walk Around’ wording and feature only applies to laying a fresh trace.
When Walk around is enabled, drag trace/via still shoves things (on my older V5).
