Bugzilla – Full Text Bug Listing
| Summary: | [debug view] Started/Exited events should always be handled (should not be skipped for optimization) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | Pawel Piech <pawel.1.piech> | ||||
| Component: | cdt-debug-dsf | Assignee: | Randy Rohrbach <Randy.Rohrbach> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | cdtdoug, dd.general-inbox, Randy.Rohrbach | ||||
| Version: | 0 DD 1.1 | Flags: | cdtdoug:
iplog-
|
||||
| Target Milestone: | DD 1.1 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Patch committed. Randy please review. P.S. This bug was created as a result of comments in bug 241317 comment #3 (point 6). DD 1.1 reelased! |
Created attachment 113934 [details] Patch with suggested fix. The view model framework abstract classes contain an optimization provision which allows the VM provider to skip processing of certain events when the events are being received by the UI in rapid succession. Currently, the suspended event over-rides other events. However, if thread-started/exited events are skipped, the view may not get refreshed as needed.