gEDA-bug: [ geda-Feature Requests-2848502 ] Advanced net selection

["SourceForge.net" <noreply@xxxxxxxxxxxxxxx>]

Feature Requests item #2848502, was opened at 2009-09-01 17:01
Message generated for change (Tracker Item Submitted) made by arndt_t
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=818429&aid=2848502&group_id=161080

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: gschem
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: arndt_t (arndt_t)
Assigned to: Nobody/Anonymous (nobody)
Summary: Advanced net selection

Initial Comment:
Hallo Werner,

i've tested the behaviour of the ->(net-selection-mode "enabled_all") with the net_selection.sch.
(Test0, Test1, Test2 is working VERY well)
I've notice some confusing behaviour:
e.g. Test 3 in the middle of the net path:
There is a net connected to "bb1" on the one side and the same net with netname "bb2" on the other side.
What should the netlister do in this case?
Which net has the prioity?
I think this beh. should not be possible (see: https://sourceforge.net/tracker/?func=detail&aid=2031198&group_id=161080&atid=818426 ).
A phy. connected net should have the same name at each segment!?

In which case the user need multible netnames?

Cheers
Thomas


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=818429&aid=2848502&group_id=161080


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