Community
Participate
Working Groups
Build Identifier: 20100218-1602 The function IWorkbenchPage.isPartVisible returns true for parts which are visible in one perspective but not in another during the switch to that perspective. So if you have a selectionListener the listener gets fired for the new selection in the new perspective. If there is a part in the old perspective listening the listener gets fired and still gets the information that its part is visible even if it is not in the new perspecive. The problem is that during WorkbenchPart.updateVisiblity first updateActivePart() is called and after that the old parts are set invisible. Reproducible: Always Steps to Reproduce: You can reproduce this with Eclipse out of the box and any view which listens to selection events (eg. History) 1. Open any perspective 2. Open the history view (leave it as active part) 3. Open another perspective 4. Open the Navigator and select a file 5. switch back to the first perspective 6. The history view shows the properties of the file from the navigator (take care that the history view is again active in the first perspective. I had sometimes problems that during perspective switch the activePart gets changed if you have the same parts in 2 perspectives. This seems to be another bug or feature?)
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.
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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.
