Description Alan Boxall 2010-11-17 10:30:36 EST

Build Identifier: M20100909-0800

This might best be described using an example.

While a debug session is active (doesn't matter what type of debug session) the F5 key becomes "Step into" globally.  Even if there are no debug views in the current perspective.  While this might seem like a feature, the problem is the conflict with F5 - refresh.  Many views rely on F5 for refresh and as long as a debug session is running it becomes Step Into.

If I customize the perspective to disable the debug command group (includes Step Into) F5 doesn't step into OR refresh. It acts as if it is bound to nothing.

NOTE: The Navigator view gets around this problem by intercepting the F5 key and forcing it to refresh.

I have included a screen cap of the Command Group Availability tab clearly showing that F5 is not available as step into.  
But as this bug shows it isn't available as the normal binding of refresh.

Debugging the platform code I discovered that F5 is bound to Step Into but when checked against the command group availability it is treated as disabled.  I would expect the binding to step into to not have occurred in the first place.

The behavior should allow F5 to stay bound to refresh.



Reproducible: Always

Steps to Reproduce:
1.Open Resource perspective "Customize Perspective" dialog.  (RMB on Resource perspective tab)
2.Choose "Command Groups Availability" tab.  
3.Ensure that the "Debug" command group is unchecked.
4.Close dialog and switch to the Java perspective.
5.Start a debug session (e.g. java debug) such that it stops at a breakpoint.
6.Make sure to switch to the debug perspective if prompted.
7.During the debug session the F5 key becomes "Step Into"
8.Switch to the Resource perspective and with focus in the Project Explorer view press F5 (it will do nothing)
9.Switch to the Debug perspective and terminate the debug session 
10.Switch back to the Resource perspective and press F5 in the Project Explorer view and it will refresh.