Bug 529740 - Segment table UX could be improved
Summary: Segment table UX could be improved
Status: NEW
Alias: None
Product: Tracecompass
Classification: Tools
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Project Inbox CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-12 09:42 EST by Genevieve Bastien CLA
Modified: 2018-01-12 09:42 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Genevieve Bastien CLA 2018-01-12 09:42:45 EST 
The segment store tables are not interactive with the rest of the views, so if there are many elements, it is very hard to make it useful.

Suggestions of improvement:

* When sorted by either start or end time, it could answer to time selections and show segments in that range

* When an actual segment is selected in one of the other views, it should select it in the table, no matter its sort order. That would mean adding segment related signals?