Community
Participate
Working Groups
When Zoom-In is requested in the control flow view is triggers a data request for the new time window and reflects the state of processes receiving events within that time interval however process not receiving events on the requested time interval should still reflect the state as per last event registered in the state model, today the state cached in the state model does not get reflected in the GUI sometimes.
Postponed to 0.6.1
Resolved, The synthetic event provider has been updated to draw the last state registered in its corresponding state provider, when multiple traces are involved within the same experiment, a loop is performed to trigger the drawing of the last state on every trace. This issue is also covering some left overs of Bug 303510, where selecting next or previous event on the first event or last event would either go all the way to the birth time of the process or the end time of the trace. These border events don't have a reference to the next event since it's out of the scope of the data collected when a zoom in / out was previously selected. The mechanism is adjusted to artificially extend these events to either half page before or after the visible time window, so moving to previous or next border events would re-select half the window before or after and therefore be able to keep the zoom level and visualise a before or after layout of information. The above required an adjustment to the tmf time analysis widget to correct a bug, when the currently selected time is in the middle of the last event of a particular process and the next event option is selected, this was causing to re-select back to the start time of the last event, the correction causes it to select to the end of the last event as it's expected.
Created attachment 173064 [details] patch
Created attachment 173065 [details] mylyn/context/zip
Committed, see comment 2, for details
Released in a past delivery.
