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

[Peter Clifton <pcjc2@xxxxxxxxx>]

Cool,

The only reason I've not pushed that code so far is that it seems to
cause some g_warnings to get fired as you shut down gschem in some
conditions. I thinl it is  related to hooks firing and causing
attributes to be updated whilst gschem is being shut down, but I'm not
100% sure. If i recall correctly, it was pango which was complaining.

Other than the g_warnings, the code works fine (and has the benefit of
splitting out the slotting implementation away from lots of special-
cased calls). Perhaps I should push the code as-is and we can fix any
warnings during the developmen cycle?

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