Net Ports: New Defaults

Post your feature requests here. Please use search function to ensure it is not here yet.
Post Reply
Message
Author
Tomg
Expert
Posts: 1541
Joined: 20 Jun 2015, 14:39

Net Ports: New Defaults

#1 Post by Tomg » 13 Nov 2015, 06:09

Net Ports need to be smarter and more dynamic. To make them easier to use, more intuitive and safer (no more unwanted Net mergers), here is how I think they should behave...

New Default #1
A new, unconnected Net Port should never have the same default name as any other new, unconnected Net Port. That is to say, when dropping a new Net Port onto a schematic, if there is another Net Port of the same type and name that already exists, the new Net Port's name should automatically be incremented to the next available unique name. For example:
1) Choose Net Port "Port1" from the standard DipTrace library and plunk it down onto a schematic. If it is the only "Port1" Net Port on the schematic, then its name should automatically change to "Port1_1" (as long as it is unconnected). See Example 1, below.
2) Choose a second "Port1" Net Port from the same library and plunk it down onto the schematic. The second "Port1" Net Port name should automatically change to "Port1_2" (as long as it is unconnected). See Example 1, below.
3) Choose a third "Port1" Net Port from the same library and plunk it down onto the schematic. The third "Port1" Net Port name should automatically change to "Port1_3" (as long as it is unconnected). See Example 1, below.

New Default #2
Once a Net Port is connected to a Net, it should immediately adopt the name of that Net (e.g. connecting Net "OUT" to Net Port "Port1_1" causes Net Port "Port1_1" to become Net Port "OUT"). See example 2.

New Default #3
If a Net's name is changed, any Net Port connected to it should automatically change to the same name.
You do not have the required permissions to view the files attached to this post.
Tom

Post Reply