Currently child event frames are only created when the following applies:
+ There's an End Trigger
+ There's a second Start Trigger that takes over
Unlike later child event frames, the first one will not end simply because its own Start Trigger condition is no longer fulfilled. This creates an inconsistency in how gaps between child event frames are handled.
E.g. PI tag BA:PHASE.1 (cycles through Phase1 - Phase7)
StartTrigger1: BA:PHASE.1="Phase1"
StartTrigger2: BA:PHASE.1="Phase3"
StartTrigger3: BA:PHASE.1="Phase5"
EndTrigger: BA:PHASE.1="Phase7"
results in the following event frame periods:
Child EF1 from the start of Phase1 to the start of Phase3 (No gap!!)
Child EF2 from the start of Phase3 to the start of Phase4 (Gap)
Child EF3 from the start of Phase5 to the start of Phase6 (Gap)
Parent EF from the start of Phase1 to the start of Phase7
Note that if there wouldn't be an End Trigger, then the first Event Frame would end at the start of Phase2, similar to the rest. But in this case there would be no Parent Event Frame and thus no Parent-Child hierarchy.
Adding a Start Trigger for Phase2 is a little clumsy as it adds extra child event frames that clutter the search results.
