Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 340071 - [perspectives] Preferences > Run/Debug > Perspectives: Bad activation on multi-select
Summary: [perspectives] Preferences > Run/Debug > Perspectives: Bad activation on mult...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-15 13:51 EDT by Markus Keller CLA
Modified: 2019-11-14 03:44 EST (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 Markus Keller CLA 2011-03-15 13:51:20 EDT
HEAD

Preferences > Run/Debug > Perspectives: When I multi-select items in the list, I'd expect to see controls to set the perspective per launch mode for any mode that is supported by any of the selected launch configuration types.

Currently, I cannot press Ctrl+A and then set the [Debug] mode to MyDebugPerspective, since a few of the launch config types don't support debugging. So I have to manually hunt for a valid selection. With the "union" approach, that's not necessary any more (launch config types that don't support a mode just won't care about the selected perspective).

BTW: There's something else wrong with Ctrl+A: When I press Ctrl+A and then Ctrl+click away all launch types but "Java Application", the Debug and Run modes still don't appear.
Comment 1 Lars Vogel CLA 2019-11-14 03:44:25 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.