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

[Krzysztof KoÅciuszkiewicz <707064@xxxxxxxxxxxxxxxxxx>]

I have fixed 1) and I believe the branch can be now merged.
Problem 2) is not blocking, as screen redraw will fix all stale pin cues.
To fix 2) properly I would have to create a generic function for traversal of connections for libgeda - this needs more discussion and is more work than I can devote to at the moment.

Note: as stated before the unconnected pins/nets now show up as red
squars in both print and screen output (bug #706552). If there's no
agreement to change PS output, this change should be removed before the
merge.

-- 
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:
  In Progress

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!

To manage notifications about this bug go to:
https://bugs.launchpad.net/geda/+bug/707064/+subscriptions


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