| Summary: | PartServiceImpl#activate() is called twice on every activation request | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Oleg Besedin <ob1.eclipse> | ||||
| Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | emoffatt, ob1.eclipse, remy.suen | ||||
| Version: | 4.2 | ||||||
| Target Milestone: | 4.3 RC1 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Oleg Besedin
Created attachment 203438 [details]
Patch
Oleg, I noticed you released this patch. http://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/?h=R4_development&id=d7c903bb8a6f67818a592cec13b61db013d83820 Should we close this bug? Yes, thank you. While the patch removed the "expensive" part of the processing, the PartServiceImpl#activate() is still called twice. It seems that the nested calls to partActivationHistory.prepend(part); UIEvents.publishEvent(UIEvents.UILifeCycle.ACTIVATE, part); are required to set up parent contexts to properly register the part as being active. This has also been fixed by the code added for bug 402073... *** This bug has been marked as a duplicate of bug 402073 *** |