|Re: [tracecompass-dev] Ideas about pin and new view features|
What would be missing ?
I understand the necessity (implementation wise) of spawning a new editor each time a view get "opened" from the project explorer but oh boy is it confusing. All editors have the same name.
It get even more confusing the moment you want to compare the same trace (N control flow view).
If I understand correctly the work flow would be to open two times the control flow view from the project explorer then activate one of the 2 spawned editors
to gain active trace status, pin one of the control flow view, activate the other tab and pin. The other way is to clone control flow view then open another event table and redo half the stuff listed above. This also introduce asymmetry between
the new view feature, which do not spawn event tables, and the open from project explorer, which spawn event tables.
To be honest, I'm not fond of it. The fact that multiple event tables have the be spawned to play in the same trace is for me a problem since, for now, there is no visual indication of link between them and their corresponding view.
Are those new event tables treated like standalone instances of a trace object (Trace open/close)?
This is something that was already brought up but discussing with Julien Desfossez, we found a functional implementation of grouping in Terminator . More information on the grouping feature in here (section 1.6 p42).
This would require a rework of the notion of opening a trace and closing it. A direct equivalent from Eclipse would the notion of opening a project or closing it.
Back to the top