Make the inner workings of UCAs more transparent
After !111, the mechanics of how we handle UCAs have changed slightly:
- UCA names are now expected to be unique. However, if the same name exists in a single file, only the last one will be used.
- Due to manner in which UCAs can now be overriden, it will be beneficial for users to see what file the action is loaded from
- In addition to the above, being able to tell when a UCA overrides an existing one will be helpful
The following examples, show how duplicates are handled both in the case where they override an existing action and when they don't. In all cases, the warning icon is simply there to inform the user why the duplicate name is not editable.
Example of duplicate names but only last one is editable
- Test123 <-(greyed out/uneditable) (warning icon here)
- Test123
- Test234
- Test534
In the above example, the first Test123
is a duplicate of the one below it, so it cannot be edited, and it will have a warning icon beside it. The next Test123
is the original and has nothing beside it
Example of duplicate names which override a system UCA
- Test123 <-(greyed out/uneditable) (info icon here)
- Test123 <-(@override text here)
- Test234
- Test534
In this example, the first Test123
is a duplicate. The next Test123
overrides a system UCA, so it has the @override
text beside it