Differences between Tdct and Capfast
This section talks about some things which make behave Tdct differently from Capfast and other things, which I noticed along the way, and essentially show my ignorance:
Default values for record properties
In Capfast compatibility mode, Tdct uses the EPICS library symbols both to establish default values for the record properties on the property sheet and for generating the database.
Capfast seems to use the EPICS library symbols to establish default values for the record properties on the property sheet, but e2db probably gets default values from edb.def.
Tdct uses a fixed snap grid of 8 units. Capfast™ uses a configurable snap grid. Unfortunately the snap grid is saved as an application parameter, not with the schematic. Because of this a change of snap grid can lead to wires suddenly being not connected as before.
There is no rotation of symbols in Tdct. Rotation functionality was implemented for bus-taps when importing Capfast™ schematics only. Drawing of new bus-taps uses standard orientation.
Wires other than buses and bus-wires are automatically numbered by Tdct, when a schematics is saved.
This was implemented because of issues in Capfast™, which led in certain circumstances to incorrect EPICS databases.
Only buses and bus-wires can have user-assigned names.
In contrast to Capfast™ tdct does not allow to connect more than one wire to a symbol port.
When re-routing a wire inCapfast™ wires would make additional connections to ports, if a segment ran over the port symbols. Tdct will only make wire-connections with wire-end-points.
Bus taps in Tdct cannot be rotated. Bus wires can only connect to vertical bus segments.