When there is one resource assigned to multiple overlapping tasks the behavior regarding which profile should be shown is not consistent. This idea adds a setting that would make it consistent. This is how the setting should work:
Scenario 1
Given a resource that is assigned to multiple tasks with different appearance profiles.
When the user activates the setting to ‘change at the end of the first task’.
Then the appearance profile only changes to the next one when the first task is finished.
Scenario 2
Given a resource that is assigned to multiple tasks with different appearance profiles.
When the user activates the setting to ‘change at the start of the next task’.
Then the appearance profile only changes when the next task starts.
This setting should probably go in the options somewhere.
I addition to this there should be a setting in the properties of the appearance profile itself to prioritize it over the others so it will be shown for the total duration of the task. If more than one is set to prioritize, or this profile is used more than once in the overlapping tasks then it should revert back to the setting above.
Is it possible to provide a .sp file with a scenario where a simple resource is assigned to multiple tasks with different appearance profiles that you typically use and then explain the desired outcome?
Each appearance profile consists of an action and the user can define the start, active, and end appearances. Each of the start, active, and end appearances has a definition of colors and transparency. The active appearance has additional settings such as growth simulation.
When the priority of the appearance profile is set, do all appearances in the profile have priority? Also - in code, I don't think we block any specific combinations of actions from being used in overlapping tasks, so it is possible to have this kind of setup and produce unexpected outcomes.
I'm happy to jump on a call to discuss, along with our UX about the use cases and how we can improve.