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

[Peter TB Brett <707064@xxxxxxxxxxxxxxxxxx>]

I'm not a big fan of the  TOPLEVEL creation hooks: I don't think we
should be adding non-reentrant stuff to libgeda at this stage. For now,
is it possible to do that setup in the normal TOPLEVEL initialisation
function?

Failing that, I suggest moving those hooks to private API for the time
being.

Otherwise, this all looks pretty fun. :-)

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