Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 34461 - [Perspectives] Action sets reset when custom perspective is changed
Summary: [Perspectives] Action sets reset when custom perspective is changed
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Simon Arsenault CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 35168
Blocks:
  Show dependency tree
 
Reported: 2003-03-10 15:57 EST by Knut Radloff CLA
Modified: 2003-03-17 16:58 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Knut Radloff CLA 2003-03-10 15:57:29 EST
build RC2

-open a Java perspective
-move the outline view to the bottom/left, below the package explorer
-"customize perspective" and uncheck the entire "Other" category
-save the perspective as "MyJava"
-move the package explorer to the right of the editor area
->Open the "customize perspective" dialog and notice how some of the "other"
action sets are checked again.
Comment 1 Eduardo Pereira CLA 2003-03-10 16:22:30 EST
Assignning to Platform-UI-INBOX since we are in the process of releasing and 
we need Nick to aprove any PR before fixing it.
Comment 2 Nick Edgar CLA 2003-03-16 14:30:13 EST
Please investigate to determine whether we need to fix this for 2.1.
Comment 3 Simon Arsenault CLA 2003-03-17 16:58:30 EST
Works as expected. When the package explorer is given focus, it has a number of 
action sets it makes visible if possible (via actionSetPartAssociations 
extension points). It ends up turning on Java Search, Java Open Actions, and 
Java Coding because these were not turn off directly by the user. If you open a 
Java perspective, go to the customize dialog, you'll notice these sets are not 
on by default.

The problem here is actions set have sorta three modes but we only really show 
2 modes. You really have on always, off always, and on/off based on active part.

It is somewhat related to bug 12216