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

Bug 363907

Summary:	Property sheet view is ignoring the correct selection on subsequent restart of RCP application when the last selection was on a blank view part.
Product:	[Eclipse Project] Platform	Reporter:	Missing name <dobromir.petrov>
Component:	UI	Assignee:	Platform-UI-Inbox <Platform-UI-Inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	dobromir.petrov
Version:	3.6.2
Target Milestone:	---
Hardware:	PC
OS:	Windows Vista
Whiteboard:	stalebug

Description Missing name

2011-11-16 08:22:10 EST

Build Identifier: M20110210-1200


The symptom of the problem is that the property sheet is ignoring the correct selection in the following use case.
We have 5 active view parts in our RCP application's perspective. When  part B is selected and the RCP app is closed
the platform ectivates part B then activates part A, but part B does not seem to see that part A is activated.
When debugging in PropertySheet::partActivated() the order of events is:

Part B Activated
Part A Activated
Part B Activated*

But clicking on Part A does not result in a part-activated event the property sheet, so its selection is then ignored.

This seems to be caused because the activation of Part B marked with * above happens as a deferred action in PartService.deferControl(IWorkbenchPartReference)
and in this deferred action, the part service does not seem to be aware of the activation of Part B, it still thinks Part A is activated.

Reproducible: Always

Steps to Reproduce:
Make sure that the clear workspace check box is unselected on the launch configuration.
1.Select a part view.
2.Close the RCP application.
3.Restart the application.
4.Select a widget inside a part view that the property sheet view is supposed to listen to for selection.
5.Property Sheet View is not populated.

Comment 1 Eclipse Genie

2018-12-20 12:50:06 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 2 Lars Vogel

2019-08-08 15:20:17 EDT

This bug has been marked with as "stalebug" for some time now. I mark this bug as "worksforme" to indicate that no work is planned here. 

If this bug is still relevant for the latest release, please reopen the bug and remote the "stalebug" whiteboard tag.