| [tracecompass-dev] Implementing multiple analysis modules for same trace type |
I'm trying to implement analysis modules for my trace, where the analysis modules both extend AbstractCallStackAnalysis. My intent is to view the results in my view which extends CallStackView (only to add a couple menu entries to the toolbar menu in CallStackView for now)
Both of these analysis modules are registered to the org.eclipse.linuxtools.tmf.core.analysis extension with 'automatic' set to false.
If I use either of these analysis modules separately they seem to generate correct data for the view.
One of these analysis modules is intended to generate intervals for all events in my trace. The second analysis module is intended to generate intervals for only a subset of the events in the trace, providing an alternate view of the trace.
My intent is that once a trace is opened, the user can select a menu entry to select which type of analysis to display in the view, and that the user can switch back and forth without having to reload the trace.
When I click the menu entry for an analysis, the Action handler invokes IAnalysisModule.schedule() for the required analysis module.
In order for the view to update at all, I have to reload the trace, but even then, it seems like I have to do it twice. I've tried this with the in-memory state model to see what happened, thinking there might be problems with lingering analysis files but that did not matter.
Looking at the documentation, I also read about an analysis module that could implement ITmfAnalysisModuleWithStateSystems in order to deal with multiple state systems in one analysis module, but I'm not sure if that helps here or how it helps.
I'm apparently missing something in the code I'm writing, but I'm not sure what.
Anyone have suggestions?
Thanks
Dave