Description John Cortell 2008-03-29 12:44:31 EDT

See attached screenshot for a storyboard explanation of the problem, as perceived by the user. This is happening with JDT and CDT, and my investigation hints at an oversight in the platform. 

EventHandlerModelProxy.dispatchResume() sets up a timer if the resume event is the result of a step operation. The purpose of the timer is to force a refresh of the viewer if the target doesn't suspend within .5 seconds. I imagine the idea is to avoid the flickering that would result between step operations if we didn't allow for some window of time for the state of the target to cycle back into the suspended state.

That's all good, but no such consideration is done for the view's actions. That is, after the .5 seconds are up, not only does the viewer need to be refreshed, but also the actions.