Bug 65352 - [ActivityMgmt] Activites preferences should update preferences tree view
Summary: [ActivityMgmt] Activites preferences should update preferences tree view
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2004-06-02 11:33 EDT by Jason Sholl CLA
Modified: 2019-09-06 16:18 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Sholl CLA 2004-06-02 11:33:30 EDT 
The preferences dialog's main tree view should be updated when the activities 
preferences page is updated and applied.  Otherwise, I need to exit and 
reenter the preferences dialog to see any new preference pages that should be 
visible.
Comment 1 Kim Horne CLA 2004-06-02 11:36:29 EDT 
This was my primary argument against putting the activity configuration into the
preference page.  I dont think we can address this for 3.0.
Comment 2 Michael Van Meekeren CLA 2004-06-02 11:49:45 EDT 
How about disabling the apply button so it does not give the wrong impression 
here?
Comment 3 Jason Sholl CLA 2004-06-03 09:52:48 EDT 
Disabling the apply button seems like a possible intermediate fix, but in the 
end I think it would be best to keep the apply button and rebuild the main 
tree view.
Comment 4 Kim Horne CLA 2004-06-07 11:53:43 EDT 
We can't do that for 3.0, but we can disable the apply button.  

Mvm:  RC3?
Comment 5 Kim Horne CLA 2008-05-02 15:10:54 EDT 
No time in 3.4
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:18:24 EDT 
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.