Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 313391 - [launch] restore defaults does nothing in Default Launchers preference page
Summary: [launch] restore defaults does nothing in Default Launchers preference page
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
: 344353 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-05-18 12:29 EDT by Darin Wright CLA
Modified: 2019-11-14 03:13 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Darin Wright CLA 2010-05-18 12:29:48 EDT
3.6 RC1

The 'Restore Defaults' button should either clear all preferred delegate setttings or be removed.
Comment 1 Pawel Piech CLA 2010-05-19 15:22:27 EDT
The fix could be difficult.  We would need to either add an API so that the preference page can reset preferences in the configuration type objects and in the LaunchManager, or we could refactor the preferred delegate logic to always read from the preference store.
Comment 2 Darin Wright CLA 2010-05-19 15:26:37 EDT
(In reply to comment #1)
> The fix could be difficult. 

Nothing needs to be done for 3.6
Comment 3 Michael Rennie CLA 2011-06-08 10:43:54 EDT
(In reply to comment #1)
> The fix could be difficult.  

Feels to me like pressing the defaults button should remove all preferred delegates - which could be done as simply as deleting the LaunchManager.PREF_PREFERRED_DELEGATES preference, then make LaunchManager a pref listener and have it clear the delegate mapping when that preference is deleted.
Comment 4 Pawel Piech CLA 2011-06-08 19:05:46 EDT
*** Bug 344353 has been marked as a duplicate of this bug. ***
Comment 5 Lars Vogel CLA 2019-11-14 03:13:44 EST
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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.