Description Anton Leherbauer 2008-07-16 08:18:08 EDT

From bug 214386 comment 14:

The ISteppingControlParticipant seems like a good idea, the only thing that
bothers me is that the contract where the participant needs to call
doneStepping() is rather vague.  I wish there was a way that the
SteppingController could call the participants when initiating the stepping,
which in turn would somehow obligate the participants to call doneStepping(). 
This doesn't really make sense though, because both the controller and the VM
adapter handle the data model events independently.  One option I though about
is to completely integrate the stepping controller into the
AbstractDebugVMAdapter.  But this would also force us to integrate the display
manager into the vm adapter, which could turn it into something of a mess.  On
the other hand it may help clarify the relationship between these.


Potential improvements for ISteppingControlParticipant to make the API contract 
more explicit:
- call participants with CountingRequestMonitor when a step command has been 
  issued
- query participants whether a step should be allowed