Prioritising certain net names (was: GND behavior)
Bug #698817 reported by
arndt_t
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gEDA |
New
|
Wishlist
|
Unassigned |
Bug Description
GND behavior
-------------
A net connection is done between two pins.
Now connect this signal to GND symbol (T crossing). Assign some netname e.g. xzy to the connection (already connected to GND) and create some netlist.
The netlister now ignores the GND connection and rename the GND net to xyz.
I think the GND connection should be prioritized!?
And the xyz named connection is now only a "user"-text-label.
To post a comment you must log in.
I agree that would be useful to make gnetlist understand that certain net names are a higher priority than others, and it could have applications above and beyond your immediate problem.