Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 344353 - [launch] Restore Defaults has inconsistent behavior in Default Launchers preference page.
Summary: [launch] Restore Defaults has inconsistent behavior in Default Launchers pref...
Status: CLOSED DUPLICATE of bug 313391
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.7   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-29 17:14 EDT by Pawel Piech CLA
Modified: 2011-06-08 19:05 EDT (History)
0 users

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 Pawel Piech CLA 2011-04-29 17:14:37 EDT 

    


    


      



        
          Comment 1
        

        
          Pawel Piech CLA

        

        
        

        
          2011-04-29 17:20:12 EDT
        

      






Build id: I20110425-1800

The Restore Defaults action has different behavior in this preference page depending on the selection in the tree: sometimes it restores the state of no default launcher selected, sometimes it does not.

To reproduce: 
- Select a launch config/mode with multiple launchers, but no default set (no checkbox set).
- Set one of the checkboxes.
- Select "Restore Defaults": 
- _Nothing happens_
- Now select the launch configuration element, which is the parent of the mode element.
- Select "Restore Default"
- In the tree select the mode element again.
- The checkboxes are cleared.

The test script states that once checked, a selection in the list should be enforced.  IMO, restore defaults, should re-set it back, as it gives the user a better sense of control.

    


    


      



        
          Comment 2
        

        
          Pawel Piech CLA

        

        
        

        
          2011-06-08 19:05:46 EDT
        

      







*** This bug has been marked as a duplicate of bug 313391 ***