Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 272367 - "Show Type Names" attribute is not available in the IPresentationContext properties
Summary: "Show Type Names" attribute is not available in the IPresentationContext prop...
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.5 M7   Edit
Assignee: Pawel Piech CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-15 15:01 EDT by Randy Rohrbach CLA
Modified: 2009-06-03 16:32 EDT (History)
2 users (show)

See Also:


Attachments
Sets DISPLAY_VARIABLE_TYPE_NAMES property in the presentation context (2.44 KB, patch)
2009-04-15 15:01 EDT, Randy Rohrbach CLA
john.arthorne: iplog+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Randy Rohrbach CLA 2009-04-15 15:01:54 EDT
Created attachment 131963 [details]
Sets DISPLAY_VARIABLE_TYPE_NAMES property in the presentation context

"Show Type Names" attribute is not available in the IPresentationContext properties. The ShowTypesAction.java action only sets the internal attribute
information of the Debug Model. Views which extend the existing views directly ( such as CDT/CDI access the attribute information directly. I could find no apparent way trying to just use Interface access to the information. I could test the Presentation context to see that it was a specific instance of DebugModelPresentationContext and then proceed from there to get the info. But this is not a very modularly independent way of proceeding.

So I have attached a changed ShowTypesAction which additionally sets the information as a property of the presentation context.
Comment 1 Pawel Piech CLA 2009-04-23 18:17:14 EDT
I would like to commit this change as it would allow DSF to observe the "Show Type Names" setting.  

Darin do you have anything against committing it for M7? I don't know if this change amounts to an API change because the property name constant is already defined, the change only causes the property value to the presentation context in addition to the debug model presentation.
Comment 2 Darin Wright CLA 2009-04-24 09:48:44 EDT
Applied patch. This is not considered an API change (everything is internal, and it is only an addition).
Comment 3 Darin Wright CLA 2009-04-24 09:48:57 EDT
Verified.