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

[Peter TB Brett <707064@xxxxxxxxxxxxxxxxxx>]

I have a few concerns with these patches.

1. is_net_fully_connected() is recursive, not iterative. Since C doesn't
optimise tail calls, it means that on designs using very complex nets we
might see stack exhaustion.

2. is_net_fully_connected() treats a netname attribute as a connection,
but that's not reflected in the doxygen comments.

3. We allocate and build a hashtable for each and every net object in
the entire design, every time we draw, which is rather expensive. Is
there any way of optimising things so that the "fully connected" flag is
only updated when a user modifies the design?

Thanks!

** Changed in: geda
     Assignee: Peter Clifton (pcjc2) => Krzysztof KoÅciuszkiewicz (k-kosciuszkiewicz)

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