If you can come up with any more net port changes that are needed, or you can see some flaws in the ideas listed above, please feel free to chime in.ĭo you mean Net Port Pin when writing net port label? Sorry for the rant, but fortunately for anyone who may be reading this thread that's all I could think of for the moment. If the net port is not connected to a net, then it should display its reference designator with a warning such as " NetPort7: not connected".Ĥ) When a net port is disconnected from a net, the net port should automatically return to its " not connected" state.ĥ) Updating a net port from its source library should do so without disrupting the current net connection. The default net port's label should display the name of the net it is connected to. The user must remember to rename the newly-placed net port before a connection can be made to a different net, which will defeat future net port component updates.Ģ) With the new-style net port, because the net port's library name doesn't change, updating the net port will actually work without causing a " Can not find component name in defined library file!" error.ģ) The default net port label should not be the net port's library name.
Current net port behavior forceably connects those two different nets together without warning and the user is typically unaware of the impending disaster that lies ahead. It's a dangerous thing to place another instance of a net port with the same library name and then connect it to a net that is different from the original net port's net. DipTrace net port characteristics need to be changed as follows.ġ) Net ports must not use their library names to force connections to each other.
0 kommentar(er)
