Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 316316

Summary: [memory] Pin Memory Monitor action not working
Product: [Eclipse Project] Platform Reporter: Justin Kong <justinko>
Component: DebugAssignee: Pawel Piech <pawel.1.piech>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: Michael_Rennie, pawel.1.piech
Version: 3.6Flags: Michael_Rennie: review+
Target Milestone: 3.8 M5   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
Proposed Fix pawel.1.piech: iplog+

Description Justin Kong CLA 2010-06-09 10:51:01 EDT 
Build Identifier: 

1. Have two Memory views opened with at least one memory monitor added
2. Toggle the Pin Memory Monitor button for one of the Memory views
3. With the other Memory view, add a new memory monitor

Both Memory views will switch to the new memory monitor. The pinned Memory view should not switch from its current memory monitor to the newly added memory monitor.

Reproducible: Always
Comment 1 Justin Kong CLA 2010-06-14 13:51:47 EDT 
Created attachment 171855 [details]
Proposed Fix

MemoryViewTreeModelContentProvider was not using the newest #updateNodes method signature from ModelContentProvider and as a result, its #updateNodes method was never being used. The fix updates the method signature and incorporates the bit mask.


As well, the if statement:
if (getPresentationContext() instanceof MemoryView)

would never return true, as the IPresentationContext is not an instance of MemoryView. Changed the method to reflect this.
Comment 2 Pawel Piech CLA 2012-01-20 01:44:16 EST 
The patch was somewhat out of date, but still correct in principal.  Thank you for the contribution.
Comment 3 Pawel Piech CLA 2012-01-20 01:45:15 EST 
Comment on attachment 171855 [details]
Proposed Fix

I forgot to update the author in the git commit, so I'm setting the iplog flag here.