Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 347481 - [debug view] Support in-line editing in Debug view
Summary: [debug view] Support in-line editing in Debug view
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.1   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-05-27 12:04 EDT by Dobrin Alexiev CLA
Modified: 2019-11-14 03:53 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 Dobrin Alexiev CLA 2011-05-27 12:04:12 EDT
Build Identifier: Build id: I20101208-1300

By convention F2 triggers in-place editing in tree views. 
Debug view should conform to the convention and allow in-place editing of elements. 
Each debugger should be able to specify if the current selection is allowed to be edited or not.

As part of custom grouping in debug view feature I'd like the user to be able to rename the group using in-place editing as well as F2 retargetable action.



Reproducible: Always

Steps to Reproduce:
The user should be able to press F2 to start in-place editing of the elements the debugger allows.
Comment 1 Pawel Piech CLA 2011-05-27 14:20:30 EDT
We currently allow inline editing only when the view is configured to show columns.  Are you also requesting that Debug view allow for column layout?
Comment 2 Dobrin Alexiev CLA 2011-05-27 14:44:27 EDT
>>> Are you also requesting that Debug view allow for column layout?

No, I don't. 

But if there is such feature I'm sure I can use it :) 
I guess in that case the debug view needs to merge column sets from differnt debuggers.
Comment 3 Lars Vogel CLA 2019-11-14 03:53:28 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.