Bug 1844 - EditorContributions disappear when View is activated (1G5NAYN)
Summary: EditorContributions disappear when View is activated (1G5NAYN)
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All Windows 2000
: P1 normal (vote)
Target Milestone: ---   Edit
Assignee: Kevin Haaland CLA
QA Contact:
URL:
Whiteboard:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2001-10-10 22:20 EDT by Erich Gamma CLA
Modified: 2002-04-17 14:11 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Erich Gamma CLA 2001-10-10 22:20:28 EDT
EG (12/8/00 5:01:52 PM)
	When a View is activate the editor contributions disappear. 
	1) create a .readme resource
	2) open it in the editor
		notice the 3 contributed actions in the toolbar
	3) click inside the outliner
		the 3 contributed actions disappear
	Activating a View should not deactivate an editor contribution. This is a regression
	and different behaviour from what we had in the tech preview.

NOTES:

KH (4/2/2001 5:48:12 PM)

	This is consistent with other applications and makes managing the menu and toolbar much 
simpler. Suggest closing this PR.

EG (4/6/01 11:51:39 AM)
	MS applications don't do this, see VisualStudio as an example.
	Where the behaviour feels really strange is when you move from 
	the editor to the outliner. Editor an outliner form a unit to the user
	and activating/deactiving contributions gives a lot instability.
	Consider this use case:
	1) select a method in Java outliner
	2) got to the editor -> editor activates its contributions
	3) select another method in the outliner ->editor looses its contributions.
	Reopended for pointing out the Content outliner/Editor problem.

KH (8/2/2001 12:58:18 PM)
	Many users (still) complain about this. Need to investigate usability issues.
Comment 1 Kevin Haaland CLA 2002-04-17 14:11:09 EDT
Fixed in latest 2.0 builds. Editor contribibutions stay around and views can, 
provide implementations for these actions. (e.g. Outline View case)

It is also possible for action sets to become visible when parts are activated. 
(e.g. User adds packages view to resource perspecitive, it is now possible for 
the refactor actionset to become visible)