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

[Krzysztof KoÅciuszkiewicz <707064@xxxxxxxxxxxxxxxxxx>]

I have something in the works for this - please see the top two patches from the attached series.
Remaining points:
* the "full connectivity" of each net should be cached for speed and recomputed when needed.
* screen redraw needs to be triggered when connectivity or net attributes change.

** Attachment added: "pin-cues.tgz"
   https://bugs.launchpad.net/geda/+bug/707064/+attachment/1899779/+files/pin-cues.tgz

-- 
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