Community
Participate
Working Groups
Call hierarchy could be extended in the way that it's behavior matches the "standart" behavior of the search view. 1) "Delete" action deletes the Java element from the *code*. This is VERY inconvenient. Expected: as in the Search view, the *search result* is removed from view. Additionally, "del" keybinding should be used by the "remove from view" context menu. 2) There is no way to open multiple call hierarchies at same time. Expected: as in the Search view, "Pin this view" button should be available at the view toolbar.
(In reply to comment #0) > Call hierarchy could be extended in the way that it's behavior matches the > "standart" behavior of the search view. > > 1) "Delete" action deletes the Java element from the *code*. This is VERY > inconvenient. Expected: as in the Search view, the *search result* is removed > from view. Additionally, "del" keybinding should be used by the "remove from > view" context menu. I agree. Actually we discussed this in the team already. > 2) There is no way to open multiple call hierarchies at same time. Expected: as > in the Search view, "Pin this view" button should be available at the view > toolbar. See bug 304135.
Fixed in HEAD. Available in builds >= N20100920-2000.
Created attachment 179242 [details] Fix
Verified for 3.7 M3 with I20101025-1800.