Bug 528157 - callstack: Make arrows more official
Summary: callstack: Make arrows more official
Status: NEW
Alias: None
Product: Tracecompass.Incubator
Classification: Tools
Component: General (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal
Target Milestone: ---   Edit
Assignee: Project inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-05 10:03 EST by Genevieve Bastien CLA
Modified: 2018-03-21 13:20 EDT (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 2017-12-05 10:03:51 EST 
Right now, arrows are a segment store in a state provider, which means 1 analyses = 2 supplementary files that can be deleted separately, so chances of an analyses not being re-run

Also, the arrows for the trace-event callstack happen to also work with the callstack group by because deep down, it's the same data and the view happens to know what to do to draw to arrows in both structures. Which is awesome and definitely should be! But if we show the group by callstack, which doesn't compute arrows, and the trace-event callstack hasn't been run, the arrows won't show, which might be confusing for the user.

Arrows should not be a o-by-way-we-have-this feature, but have a real central place to be.

What? It needs to be discussed. I made a DependencyAnalysis 6 months ago that didn't make it yet to the Incubator to compute only arrows, so each arrow set would be in a separate analysis.