Community
Participate
Working Groups
Go to Problems view, change filter to "any element in the same project", click on a project (markers for its files are shown in the Problems view). Use "Open in New Window" on the project. Project is opened in new window, but no problems are shown in the Problems view. Problems appear if any resource was selected in the Package Explorer view. The selection is empty after project was opened in New Window. We have similar view which content depends on the selected project, and it has the same problem with "Open in New Window" scenario. Is it possible to change initial selection, e.g. select the project by default?
I don't think so. The new workbench window contains a completely new set of views ... i.e. the package explorer in one window doesn't know about the package explorer in the other window. PW
Well, the new Package explorer does not know about others, but it knows that it is opened on certain project.
A newly opened package explorer does not have a current selection. PW
Oh, I see what you mean ... it opens drilled down to the project that was select, but has no selection. Moving to JDT for comment. PW
BTW, the Navigator view has the same behaviour; potentially - CDT has similar views, etc. Not only the Package Explorer.
The current action opens a new window with the current perspective id and sets the page input to the project - OpenInNewWindowAction Later, PW
This means that when the Problems view is being created, it can use the page.getInput() method and show problems accordingly. (if selection is empty). Just tested it with my view - this approach works. Not sure if there are no side effects. Are there reasons why the Problems view does not use the page input?
Assigning to component owner PW
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.
