This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
The Debug Menu now has a Stack pullright containing Make Callee Current and Make Caller Current. Make Caller Current should be the top item for two reasons: - its the only one enabled when your program first stops - it is used much, much more frequently than Make Callee Current
this is problem of UI spec. => David John can you look at it, please? see: http://ui.netbeans.org/docs/hi/debugger3.4/toolbarmenu/index.html
I don't think this is a problem. Here is why: - Reversing the order is odd because it places the action that makes you move "up" in the stack below the action which moves you "down" in the stack. Directionality may be undesirable, but reversing these actions will fight against the directionality that is implicit in these actions. - If you've gone so far as to use the menu to get at these actions, I don't believe that the fraction of an inch of motion it would take to get at this action in the second position is a significant amount of work.
Arrggg!!!! This is one of the reasons Up and Down should not be part of the paradigm of moving around in the stack! > If you've gone so far as to use the menu to get at these actions, > I don't believe that the fraction of an inch of motion it would > take to get at this action in the second position is a significant > amount of work. You aren't serious are you? It is MUCH easier to go straight right than it is to go over and down. A fraction of an inch is not the issue, turning the corner is. Of course, if you take the diagonal route and drop down too quickly then the pullright menu will go away and you get do it all again. I thought the goal was to make common things easy to do. It is MUCH more common to do Make Caller Current than to do Make Callee Current. I would guess by a factor of 10:1. Is the conclusion that this menu exists simply to display the actions and their shortcut keys and not really to be used? In that case, issue 22174 should also be implemented.
Since this functionality is also directly available from the stack view (and, allows more context and easier multi-function jumps there as well), we felt it wasn't that important to put the actions in the toolbar. It seems a little redundant there. For the same reasons I'm less concerned about these actions existing in a submenu (and, I agree, I overstated the ease of getting to items in submenus, though I wouldn't call it 10:1)
Resolved for 3.3.x or earlier, no new info since then -> closing.