| Summary: | [detail pane] Move detail formatter actions to detail pane | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Darin Wright <darin.eclipse> |
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 3.3 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | stalebug | ||
|
Description
Darin Wright
The problem with accomplishing this is that the selection provider for the default detail pane is different than the view's selection provider. The detail pane provider just provides the current text selection, so detail formatter actions contributed to the detail pane don't know the currently selected object (so the enablement fails). It might be possible to workaround this by creating a special selection that combines the text selection and the current object, but this would affect many other actions. Changing the selection could have serious consequences for other contributed actions. This does seem problematic... using the new menus extension point I am able to create a command for "New Detail Formatter" that appears in the detail pane popup menu only when we are debugging Java, but I can't get the "handler" to enable properly, as the IHandler is not given a context for enablement (i.e. to enable based on the selection in the tree). Using an IViewAction (popup menu view contribution), we can have the action delegate listen to the selection in the variable view tree, but we can't get the visibility right, as the visibility is based on the text selection... not committed for 3.3 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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. -- The automated Eclipse Genie. |