If you don't understand what it is trying to do then you'll be either fighting it all the time or trying different things out because that worked, once, last week.
I can't even
begin to imagine where you got that from. You connect things and they're connected.
You don't and they aren't. If they aren't but look like they are (such as might happen with a move or a
symbol edit) they get flagged so you can correct them and make sure they aren't errors in the making.
I absolutely cannot comprehend how you get a recipe for confusion and conflict out of a few simple rules
like that.
But my post above, which you quote, is asking how essentially how it decides you've 'metaphorically
clicked a button'
Work with me here and avoid speaking in metaphors. What does that mean? You're clicking a button or you aren't.
and the design is as you want it, or you're still working on it. It's quite common to be modifying the design as you go along (that's why we do it all in CAD rather than scribbling it on a fag packet before drawing it up so it's Right First Time). Often I will insert a resistor or remove it or have hanging nets because, well, it's being designed innit. I don't mind a little red icon pointing out some unfinished business (but tend to ignore them anyway because, well, it's being designed and I know it's not finished). But if I had to manually ack every such case I'd be rooting away in settings to find the relevant tickbox to untick.
So it's not clear to me at all what benefit (other than the one nctnico spelled out about overview maps) being hassled to ack something every time I make a change brings.
I certainly didn't mean to imply that the UI was going to freeze up on you and refuse to let you do anything
else until you clear the error/warning - you're entitled to leave as many of those warning dots in place as you
wish while going about other business. I mean, nobody expects the Spanish Inquisition here. Clean 'em up
now, or clean 'em up later. You do you.
And, while we're here, I really hate the Kicad GUI. In fact, that's the major reason I am not making things with it. But I hate gesture-based interfaces just as much because you can end up commanding something unintentionally. And even intentionally, you can command the wrong thing. Just to keep this on topic
Agreed. The irony here is that my personal opinion being that everything that isn't strokes pretty much
sucks goat ass isn't actually affecting my choice not to use KiCAD (yet) - that choice is entirely due to
the netlist-ignorance problem. In my limited experience I found it confusing and inconsistent, in part
because when I thought I was making connections they didn't
behave as though they were... which
turned out to be correct. And in general terms, drop-down menus taller than my screen is high, commands
that seem to half-overlap other commands, and hot-key lists longer than I think it reasonable to memorize
say to me "it looks like people just keep adding shit" rather than "this is governed by a thought-out UI
philosophy". But honestly, I could live with a lot of that if only I could trust what I see on the screen.
Wrt strokes, I'd be interested in hearing more about your experience and why you don't like them. Sure,
I muff strokes when I get going too fast and the gestures get a little too sloppy, but you can always escape
a function before it does anything you don't want, and if you don't, there's an undo queue - you just back
up as many steps as necessary with the Undo stroke. Hardly happens, though, I more often just find myself
selecting the wrong things because the select filter maintains state and want to move a symbol or text when
I last moved traces and vias and left it set for those.