Re: [platform-debug-dev] IBreakpoint listener API

[Darin_Wright@xxxxxxx]

I agree with this proposal - there needs to be a way to fire a breakpoint change notification when a breakpoint's underlying marker has not changed. However, I would name the method #fireBreakpointChanged(...) as to avoid overlap with the IBreakpointListener interface (which defines #breakpointChanged).

Null should be acceptable as a marker delta parameter. I believe we already use null for this value, and the spec should reflect this.

Created a bug to track this feature:

http://bugs.eclipse.org/bugs/show_bug.cgi?id=10218

Darin

Jared Burns <jared-eclipse@xxxxxxxxx> Sent by: platform-debug-dev-admin@xxxxxxxxxxx 02/25/2002 09:16 AM Please respond to platform-debug-dev

To:        platform-debug-dev@xxxxxxxxxxx         cc:                 Subject:        Re: [platform-debug-dev] IBreakpoint listener API

Upon further examination, I realize that I shouldn't be worried about 
manually notifying listeners of breakpointChange events. The 
BreakpointManager should take care of this for me - it maintains the list of 
listeners and is the one responsible for firing notifications when the marker 
changes.

I think we should add API to the BreakpointManager (BPM) to allow 
third-parties to notify the BPM of breakpoint changes. I suggest adding 
breakpointChanged(IBreakpoint) to the API. This method would notify all 
IBreakpointListeners via the breakpointChanged(IBreakpoint, IMarkerDelta) API 
with a null marker delta. Note that this is the way 
BPM#breakpointAdded(IBreakpoint) and BPM#breakpointRemoved(IBreakpoint) 
already behave.

The IBreakpointListener API still needs to be updated to accept null as a 
parameter.

- Jared
_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-debug-dev