so this seems to be the better approach for dealing with this insidious problem. In some cases -- as here most prominently with the root track within the timeline -- we have to care within the domain model to prepare unique ids even for sub objects treated as attributes. In the actual case, without that special attention, all timelines would hold onto an attribute "fork" with the same ID, based on the type of the nested object plus the string "fork". Thus all root track representations in the GUI would end up listening to the same ID on the UI-Bus... |
||
|---|---|---|
| .. | ||
| draw | ||
| DIR_INFO | ||
| empty.html | ||
| InterfaceConcept_Varga.mm | ||
| renderengine.html | ||
| thinkPad.ichthyo.mm | ||
| uml | ||
| workflow.mm | ||