Overwrite Default Aspect at Formal Instance Child Object
I have some "composite" Control Module Types in Control Builder M that consist of multiple Control Modules with their own Graphics Aspects. Now i want to adjust/overwrite some of the Graphic Aspects for these Children Objects, which is possible in the Object Type Structure at the Formal Instance List that holds these Childrens as well. However the result is that there are then duplicated Objects existing at the Instance, both the Original Aspect from the Basic Control Module Type and the overwritten Aspect from the Child under the Formal Instance List.
This is usually not a Problem, however for the Default Aspect (i.e. the Faceplate) this means that the Original Faceplate will be called instead of the overwritten (duplicated) one.
Anyone has a good idea for a workaround?
Voted best answer
Can you attach a picture or document of the problem so that I can see how the object types and formal instance lists have been configured and how "the final result" looks like?
Aspects belonging to locked standard libraries can not be removed - adding new custom will co-exist side by side.
If possible, have your types checked by the Consistency Checker tool.
The default aspect key suggested by Boris has been superseeded by "Aspect Precedence Lists" as of 800xA v5.0. The "Default Aspect Key" still exists, but is last in search order.
By creating a new aspect category for your custom faceplates, you can insert that category before the standard faceplate aspect category. Please note that an APL can refer to another APL, e.g. the "Process Graphics PG2 APL" is referred from the Default Precedence List.
Last: different users can be configured with individual APLs, or even be controlled via nodes or node groups. E.g. a large screen workplace used for display on a wall may have different APLs than the regular operators have, etc.