Add output to type specialization structure that outputs the number or name of the subdiagram executed

[jacemdom]

Usefull for debugging misfiring or overifiring frames when building a VIM with a lot of datatypes. Could simply output the frame number

Or could also output the complete frame name as a sting so that if the frame names become partially editable as suggested here, all would be coherently managed.

[TomOrr0W]

I am not sure if I support the idea itself, but it would make sense to keep it specific to the type specialization structure.  I believe this is the only structure that is always used in non-debuggable inlined vis (they can be placed in non-vim vis, but they have no real use there).  For anything that is not inlined, you can just turn debugging on and put a probe in the structure

[wiebe@CARYA]

@TomOrrOW:

Probably best to stick to just TSS for now. We can raise the bar later .

OT:

Spoiler

 I do see a use case for event structures. For instance, audit trails can be a pain to make, as you need to duplicate code in each and every event case. So an output would be helpful in some corner cases. It is possible, but tricky, to (mis)use the event manager's API for this. But still...

 What would be the down side? I don't see any, besides the cost of development resources?