Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 303510 - [LTTng] Information not refreshed when moving outside the current visible range
Summary: [LTTng] Information not refreshed when moving outside the current visible range
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: LinuxTools (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Alvaro Sanchez-Leon CLA
QA Contact: Francois Chouinard CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 301629 301630
  Show dependency tree
 
Reported: 2010-02-22 11:34 EST by William Bourque CLA
Modified: 2022-01-13 14:53 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description William Bourque CLA 2010-02-22 11:34:06 EST
When uising the resources view and/or the control flow view, moving with the arrow might cause certain part of "ribbons" to not be refreshed correctly. 
In particular, when the move bring the cursor outside the visible range (i.e. a part that is not currently in the screen), some events are missing and so the ribbons color might not be what it should. Zooming In or Out bring back the ribbons to a consistent state. 

There is possibly missing a data request for case where the cursor move out of the range.
Comment 1 Alvaro Sanchez-Leon CLA 2010-03-03 09:13:36 EST
Today the relevant state information is stored in time interval objects (e.g. Start time and duration), due to the large number of state transitions we can not load all time intervals in memory so each time a zoom in / out action is triggered a new data request is triggered to remove the existing interval objects and replace them with the information received in the request. However when left / right arrows are used, the widget moves along the objects loaded in memory which works fine as long as we move within the current time window. Once we move outside the current time range window the location is moved to the next square in memory which is either at the beginning or at the end of the trace. 
   Due to the large number of information a data request covers only the specified time range, so the widget does not know what is the previous / next relevant event outside the requested time frame, so moving to the end / beginning of the trace will continue to be the alternative, however we can trigger a data request so the information displayed at the beginning or end is complete.
   
This behaviour has been implemented now in the "refactor" branch, this bug will transition to fix once the branch in integrated back to the TRUNK
Comment 2 Francois Chouinard CLA 2010-05-17 15:48:38 EDT
Merged with trunk.
Comment 3 Francois Chouinard CLA 2010-07-08 10:34:57 EDT
Released in a previous delivery.