| Summary: | Update the migration guide to notify adopters about the changes to the 'Properties' view regarding post selection events | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Remy Suen <remy.suen> | ||||||
| Component: | UI | Assignee: | Prakash Rangaraj <prakash> | ||||||
| Status: | VERIFIED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | daniel_megert, ob1.eclipse, prakash | ||||||
| Version: | 3.7 | Keywords: | Documentation | ||||||
| Target Milestone: | 3.7 RC4 | ||||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Remy Suen
For the reference, this originated from the bug 339360 . Created attachment 196977 [details]
Patch v01
Is this fine or should we provide more detailed information? (In reply to comment #2) > Created attachment 196977 [details] > Patch v01 This text is of interest to plug-in developers if they wish to ensure that the 'Properties' view is "optimized" when their view has selections that has properties to show. However, the main underlying problem is that clients that implement IPostSelectionProvider must actually fire post selection events. If they don't forward this event properly then their 'Properties' view may not work. Those that simply implement ISelectionProvider will work as they did before, it is just a problem for those who implement IPSP but does not actually fire post selection events that will be affected by the change in the 'Properties' view's selection handling. (In reply to comment #4) +1. Minor issues: - the copyright date is wrong. - write "view" with lowercase ==> Properties view Created attachment 197123 [details]
Patch v02
Patch applied to CVS Head. The ´ character introduced a CHKPII error. I've fixed that for I20110602-0800. (In reply to comment #8) > The ´ character introduced a CHKPII error. I've fixed that for I20110602-0800. Thank you! np. Glad to help! I guess at some point we should set the encoding on the project(s) and check it into CVS. Verified in I20110602-1051. |