Bug 2631

Description Nick Edgar 2001-10-10 22:40:18 EDT

Eclipse corner post by VP: Views should be displayed in historical order, 

I have a defect opened against my component which I think should be routed
to eclipse.
This is the scenario :
- I have tree views A, B, C opened in that order, one on top of each other.
- Select view B and do some work on it
- Select view C, do some work than close C
- At this point I expect B to be the visible view because this is the last
one I was looking at; instead view A is the visible one.
This is very confusing and disorienting when you try to follow some
information which should be navigated in a certain order.
Can this problem be solved ( or is any workaround I can use )?

NOTES:

NE (7/25/01 11:14:18 AM)
	Replied:
This does indeed sound disorienting: it always activates the first one in
the group.
I've filed a PR for it.  Unfortunately, there is no known workaround.

Do you think the intuitive behaviour is to activate the previously active
view (historical order), or to activate the previous (or next) one in the
shown tab order?

NE (7/30/01 9:49:22 AM)
	VP replies:
Thank you Nick

From my experience, I think the view that should be activated is the
one previously active. The reason is that you might have some other views 
opened, but never used them (you didn't noticed they are opened or just
didn't bother to close them), so activating these views instead of the
ones you really used can be confusing.
In a trace scenario this is very confusing because the order you navigate
the views is very important.

Could you please send me the PR number so I can attach to my defect.

NE (7/30/01 9:51:51 AM)
The point about never seeing views which the user did not explicitly activate is interesting.
It also means that the view's plugin would not be activated unnecessarily, minimizing footprint.

The PR number and title is:
1GHFAFW: ITPUI:WIN2000 - EC: Views should be displayed in historical order