gEDA-bug: [Bug 707064] Re: Remove unconnected net cues for netname connected nets

[Peter Clifton <pcjc2@xxxxxxxxx>]

See (not 100% complete) "attribute hook" work here:

http://repo.or.cz/w/geda-gaf/pcjc2.git/commitdiff/2156a7294a1aeaf4b97f6d6d5e7da3d584acd296
and
http://repo.or.cz/w/geda-gaf/pcjc2.git/commitdiff/308016b93bba3882f67c228cfd42acf6a7e9740a

NB: These URLs will be out of date if / when I push any changes to my
stgit branch, sorry.

They live in this branch:

http://repo.or.cz/w/geda-
gaf/pcjc2.git/shortlog/refs/heads/local_customisation

And are titled:

"Attribute change hooks"
and
"Perform slot updates based on attribute changed hooks"

-- 
You received this bug notification because you are a member of gEDA Bug
Team, which is subscribed to gEDA.
https://bugs.launchpad.net/bugs/707064

Title:
  Remove unconnected net cues for netname connected nets

Status in GPL Electronic Design Automation tools:
  New

Bug description:
  This came up after a presentation with potential users.

  The red cues on the end of unconnected net was perceeved as a nice
  warning that something was unconnected.

  Their expectation was that a net connected at one end should lose the
  second cue (on its unconnected end) if the net is named. This could be
  implemented either to mean "has a netname=" attribute, or that it is
  connected to something which has one.

  This helps to preserve the semantic that "red splodge" == something to
  fix.

  We also noted that the pin cues were not nearly as visible as they
  ought to be when projected!


_______________________________________________
geda-bug mailing list
geda-bug@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-bug