Hello Joshua,
first of all I wouldlike to praise you: A great program that is really easy to use. Excellent!
I think it is morecorrect to provide the terminals with dynamic texts.
The main task of theterminal diagram is to show which terminal is connected to which terminal on the device. Only secondarily must it be shown which cable is used for this purpose.
Entering the targetname (of the device connection) by hand is from my own experience very error-prone and should be avoided. Sometimes the biggest weakness in QET at the moment.
I also believe theproblem of multi-level terminals and multi-terminal terminals on one potential could be solved by naming the terminals as well:
multi-levelterminals
-X23: 11/1Terminal a ! -X23: 11/1 Terminal b
-X23: 11/2Terminal a ! -X23: 11/2 Terminal b
-X23: 11/3Terminal a ! -X23: 11/3 Terminal b
Terminals withmultiple connections on one potential
-X23: 11Terminal a ! -X23: 11 Terminal b
-X23: 11Terminal c ! -X23: 11/1 Terminal d
A graphical designwith the terminal block generator is very difficult, which is why I would prefer a solution with a table.
In the upper part ofthe table, a space could be created where the user can insert a schema image of the terminal. Here you can see the names of the connections (terminals). So everyone can designate the terminal and the connections (terminal) as he thinks it is most correct.
We are welcome todiscuss it.
I hope you continueto enjoy creating your fine program!
Greetings from UpperSwabia
Xander
p { margin-bottom: 0.25cm; line-height: 115%; background: transparent none repeat scroll 0% 0%; }
ps.: I hope my translation is correct...
