Terminal number position (sorting) in terminal manager

I started doing some experiments using the new terminal block functionality as well.  I really like the new workflow and looking forward to making use of it.  So first a big thank you to Joshua and keep up the good work!

But there are some basic conceptual / design issues where I simply don't see how this can be applied to my schematics.

For connections to external equipment, where one terminal block has the outside cabling 1:1 on the bottom row, with connections to internal ports on the top row, I think this works pretty well already.  But beside the numbering / sorting issues here, I think we should consider how the terminal symbol's label is handled / parsed.  I put some terminals on the folio, e.g. "X10:1" to "X10:12".  These need to be labelled on the folio itself, at least once with the block (X10) and each terminal with the number.  So each terminal symbol already has all the info contained, where the block and number are separated by a colon ":".

The way it is shown in the last video link, each terminal only has its number as the label.  But this means that on the folio where it is placed, there is no actual hint on which one it is, as the number could appear on any block (e.g. "X10:1", "X21:1", "X25:1").  In addition, not having the block naming in each terminal's label makes it impossible to automatically process them, like generating overviews (as with my qet_terminal_tables script) from the database.  So I think the traditionally used labels like "X10:1" are the better approach.  I could see the terminal manager to automatically parse the first part (prefix) to move the terminals to the correct group.  Then the label *within* this group should just be the number (suffix).  At that point, sorting would work again as with simple numeric labels.

The second problem I see is that each terminal symbol generates its own entry in the manager.  There is some special handling for multi-level terminals, which is nice.  But what about potential distribution, where you need a central GND or +24V terminal block to connect all the equipment, each device with one wire.  The devices will be shown on different folios.  I'll use both connection points of one terminal (or even 3 or 4 points with the larger ones) in very different places.  So the terminal "X10:1" will be placed twice, on two different folios, with the same label.  What I usually do is to put a "1a" or "1b" text on each, to show which connection point (top or bottom) the wire ends at.  Even worse, with four connection points there will be "1c" and "1d" as well.

In that case, there will be four terminals shown in the terminal block manager, which really all represent the same physical element.  Just that its four connection points are used for wires to independent devices.  How would I handle that, so the generated terminal block drawing has only one column for all four of these connections?  Ideally, it should show the cross-reference (folio number) for each associated symbol, but only one physical "slot".

This is really about the data model used by the terminal manager.  I guess several terminal *symbols* with the same label should be grouped automatically and only result in one generated *physical* terminal.  Properties like terminal kind and function should be synced among the group, unless the entries are assigned to different levels.

@Joshua, what do you think about this?  Are there plans already to handle such cases?  Frankly I don't see how the current data model maps to anything but the most basic schematics with only a handful of terminals.  Failing to sort by numbers is only one symptom of this, because the labels are not "interpreted" in any way.