If a task for EV1 and a task for EV2 must begin at the same time, we need a sync point. There are two ways to do this.
The first way is to add a field in the task form, asking for an identifier (a number? a text field?). Then if the same identifier is used between two actors, it'll form the table appropriately to display those two starting at the same time/height.
The second way is by inference based on PET and the duration of previous tasks. If two tasks start at the same PET, you may infer that the timeline author planned for the two actors to begin these tasks at the same time. While it may actually not be required that these events be in sync, it doesn't hurt to have them formatted as such in the detailed table output.
Use the following to update Template:Actor 2 Task (and 1 and 3). This adds Property:PET Start, which helps determine an inferred sync point, except for the last task in the timeline. Because the get-ahead time is calculated outside of this by the parser function, the final task for each actor will not pick up a sync point using this method. I'm not sure just yet how to handle that part.
<noinclude>
This template is used with the Summary Timeline form.
[[Category:Template Used for Summary Timeline Extension]]
</noinclude><includeonly><!--
-->{{#vardefine:Index|{{#counter: Actor2 }}}}<!--
-->{{#ifeq: {{#var:Index}}|1|{{#vardefine:PET|0}}|}}<!--
-->{{#set_internal:Task
|Index={{#var:Index}}
|Actor={{#var:Actor2name}}
|Has text title={{{Title|}}}
|Assigned to#list=Actor2
|Duration={{{Duration hour|00}}}:{{{Duration minute|00}}}
|Duration hour={{{Duration hour|00}}}
|Duration minute={{{Duration minute|00}}}
|Duration in minutes={{#expr: (({{{Duration hour|0}}} * 60) + {{{Duration minute|0}}}) }}
|Related article#list={{{Related article|}}}
|Color={{{Color|}}}
|Free text={{{Free text|}}}
|From page={{FULLPAGENAME}}
|EVA title={{#var:EVATitle}}
|Parent related article#list={{#var:pageRelatedArticle}}
|EVA Duration={{#var:EVADurationHour}}:{{#var:EVADurationMinute}}
|Color White Meaning={{#var:ColorWhiteMeaning}}
|Color Black Meaning={{#var:ColorBlackMeaning}}
|Color Gray Meaning={{#var:ColorGrayMeaning}}
|Color Red Meaning={{#var:ColorRedMeaning}}
|Color Orange Meaning={{#var:ColorOrangeMeaning}}
|Color Yellow Meaning={{#var:ColorYellowMeaning}}
|Color Blue Meaning={{#var:ColorBlueMeaning}}
|Color Green Meaning={{#var:ColorGreenMeaning}}
|Color Pink Meaning={{#var:ColorPinkMeaning}}
|Color Purple Meaning={{#var:ColorPurpleMeaning}}
|PET Start={{#expr:0+{{#var:PET}}}}
}}<!--
-->{{#vardefine:PET|{{#expr:{{#var:PET}}+{{#expr: (({{{Duration hour|0}}} * 60) + {{{Duration minute|0}}}) }}}}}}</includeonly>
If a task for EV1 and a task for EV2 must begin at the same time, we need a sync point. There are two ways to do this.
The first way is to add a field in the task form, asking for an identifier (a number? a text field?). Then if the same identifier is used between two actors, it'll form the table appropriately to display those two starting at the same time/height.
The second way is by inference based on PET and the duration of previous tasks. If two tasks start at the same PET, you may infer that the timeline author planned for the two actors to begin these tasks at the same time. While it may actually not be required that these events be in sync, it doesn't hurt to have them formatted as such in the detailed table output.
Use the following to update Template:Actor 2 Task (and 1 and 3). This adds Property:PET Start, which helps determine an inferred sync point, except for the last task in the timeline. Because the get-ahead time is calculated outside of this by the parser function, the final task for each actor will not pick up a sync point using this method. I'm not sure just yet how to handle that part.