Community
Participate
Working Groups
To separate data from representation and prevent high CPU resources consumption every time then view is opened, CP should be calculated once and then saved in model until events flow is changed. New set of containers should be added in model for CP storing.
Could this enhancement not leverage the existing thread interaction views? These views build from the trace model and are exploited for this kind of visualization in extending products for thread/process/machine interactions. Showing messages between the threads (logical thread objects in the view) gives the same end result. Since this is a time based analysis, using the time based viewers seems to make sense.
Note, if this enhancement is a work item of 200320, it should be marked as a defect. Otherwise (e.g. new function not covered by 200320), you will have to request AG and PMC/PG approval to include them in 4.5.
(In reply to comment #2) > Note, if this enhancement is a work item of 200320, it should be marked as a > defect. Otherwise (e.g. new function not covered by 200320), you will have to > request AG and PMC/PG approval to include them in 4.5. > This was originally opened as an enhancement.
Deferral to future with PMC approval
Mass update of P1 enhancements and defects targetted to future to P2.
Retargeting to 4.7.2
No plans to fix at this time.
This defect had been resolved as WONTFIX for more than 1 month. Closing this on the reporter's behalf. Please re-open if you have further comment on this issue.
Closed in TPTP 4.7.2.
