Mail Archives: geda-user/2012/12/07/14:27:52
On Wed, 2012-12-05 at 15:32 -0500, DJ Delorie wrote:
> For the record, I typically use 'f' to highlight *nets*, not
> *connections*. I.e. I use it during routing to highlight what
> *needs* to be connected, not what *is* connected.
> IIRC there were valid reasons for the change, but I also think we need
> some way to highlight everything in a *net* during routing.
> Hopefully, the "hightlight/find" options in the net dialog still
> perform this function.
>
> Maybe "highlight all rats in this net" would be useful too.
I'm wondering if we could split the colouring to differentiate what _is_
connected to the object under the cursor when we invoke the "F" action,
and what "should be" connected.
Solid green for "actually connected" to the point in question, and a
muted or hatched green for "should be connected".
We can argue whether the "FOUND" flag is applied to the "should be" or
"are physically" connected group.
We are already attempting to hight shorts in orange when optimising the
rats-list, but we don't do a very good job at identifying the actual
short location.
Re-colouring these pins on the invocation of the "find" action might
help. As pads / vias know which net they "should" belong do, we can make
the "WARN" colouring of "found" objects relative to the pin / pad the
user is hovering over.
--
Peter Clifton <peter DOT clifton AT clifton-electronics DOT co DOT uk>
Clifton Electronics
- Raw text -