Community
Participate
Working Groups
I have two similar perspectives. I would like to add the same views to an IFolderLayout in both perspectives, but have the visible view be set differently. This will give my users a sense of continuity. As far as I can tell the visible folder is defaulted to the first one added to the group. Is that correct?
That should be "visible view is defaulted".
Yes, they are appear from left to right in the order added (at least, in LTR locales), and the first is selected by default. Since you probably don't want to change the order of the views, new API will be required to specify the selected one. Note I'm saying "selected" instead of "active". There can be multiple folders and top-level views in a perspective, and only one can be active. There's also no control currently for specifying which part is active. The current behaviour is to keep the active part from the previous perspective active, if it can, or to activate the view at top left if not.
So we're clear, I am not asking for API to control which view is active. I just want to be able to control which view in an IFolderLayout is selected.
Reassigning bugs in component areas that are changing ownership.
There are currently no plans to work on this feature. PW
Changes requested on bug 193523
My workbench terminology seems too be weaker than I thought from this bug. So for a selected view that isn't active, we're talking about a view that's at the top of the stack and visible to the user but that's currently not active (with the white outline instead of the "blue" outline), correct?
(In reply to comment #7) > My workbench terminology seems too be weaker than I thought from this bug. So > for a selected view that isn't active, we're talking about a view that's at the > top of the stack and visible to the user but that's currently not active (with > the white outline instead of the "blue" outline), correct? yes ... having a new perspective show a view in the stack other than the first tab. 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.
