Input interactions can sometimes trigger a state transition. When this occurs,
the task should not be made into a Gui Tree trace. Instead, two new tasks
should be scheduled: a first one missing the triggering input and second one
with that input in place of the scheduled event.
Example: let be task T the sequence of actions (A1, A2, A3) with A3 being the
sequence of inputs (I1, I2, I3) followed by event E, that is
T = (A1, A2, (I1, I2, I3, E))
Let's suppose that I2 is actually an event that trigger a state transition. If
and when this is detected, trace T should be discarded immediately and two new
tasks should be scheduled:
T1 = (A1, A2, (I1, I3, E))
T2 = (A1, A2, (I1, I3, I2))
where I2 is now obviuosly the event for trace T2.
Detection is achieved by the usual Extraction->Abstraction->Comparation routine
iterated for all the interactions rather than only for the final event.
Original issue reported on code.google.com by nofatclips on 4 Jun 2012 at 9:13
Original issue reported on code.google.com by
nofatclipson 4 Jun 2012 at 9:13