RE: [platform-debug-dev] viewContribution override

["Rick Marion" <rick@xxxxxxxxxx>]

Thanks.

That may be the way we need to go.  We've been considering virtualizing
the breakpoints (as well as the markers) as you indicate below.

-----Original Message-----
From: platform-debug-dev-bounces@xxxxxxxxxxx
[mailto:platform-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of Pawel Piech
Sent: Tuesday, October 07, 2008 11:39 AM
To: Eclipse Platform Debug component developers list.
Subject: Re: [platform-debug-dev] viewContribution override

IMO, you'll have better luck introducing a UI which shows "pending" 
breakpoints for your debugger.  (I.e. breakpoints which are set to be 
added or deleted when the state of the target changes). 

For better or worse, breakpoints in Eclipse are shared between many 
different debuggers built on this framework, and generic user actions 
such as this one, cannot be (realistically) customized.

Cheers,
Pawel

Rick Marion wrote:
> Our debugger wraps a (multi-processor) chip that doesn't allow
> breakpoint setting or clearing unless the target processor(s) are
> halted.    I would like to grey-out or remove the "Delete All" menu
item
> if there are breakpoints set in any running processors.  The current
> condition for enabling the "Delete All" menu item is if the breakpoint
> manager has (registered) breakpoints.
>
> If there's a way to intercept the dialog, replace it with my own and
> always return "no" (when breakpoint are set in running processors)
that
> would be fine.
>
> Thanks
>
>
>
>  
> -----Original Message-----
> From: platform-debug-dev-bounces@xxxxxxxxxxx
> [mailto:platform-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of Darin
> Wright
> Sent: Tuesday, October 07, 2008 10:52 AM
> To: Eclipse Platform Debug component developers list.
> Subject: Re: [platform-debug-dev] viewContribution override
>
> What's your "condition" for allowing the action to be performed?
>
> Note that there already is a user prompt to confirm deletion - which
can
>
> be set to always/never prompt.
>
> Darin Wright
>
>
>
>
> "Rick Marion" <rick@xxxxxxxxxx> 
> Sent by: platform-debug-dev-bounces@xxxxxxxxxxx
> 10/07/2008 12:42 PM
> Please respond to
> "Eclipse Platform Debug component developers list." 
> <platform-debug-dev@xxxxxxxxxxx>
>
>
> To
> <platform-debug-dev@xxxxxxxxxxx>
> cc
>
> Subject
> [platform-debug-dev] viewContribution override
>
>
>
>
>
>
> Hello,
>  
> I need to intercept the BreakpointView's delete all action as shown in
> the 
> context menu and conditionally allow the action to be performed. 
> I can see no mechanism for overriding an existing action, just 
> contributing new actions. 
>  
> Another approach would be to override the DebugPlugin's
ViewContribution
>
> class for removing breakpoints.   Is there anyway to override a 
> ViewContribution installed by a previous loaded plug-in.
Specifically,
> I 
> would like to override the 
>
org.eclipse.debug.internal.ui.actions.breakpoints.RemoveAllBreakpointsAc
> tion 
> defined in the ui's XML.
>  
> Regard,
>  
> Rick_______________________________________________
> platform-debug-dev mailing list
> platform-debug-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/platform-debug-dev
>
>
> _______________________________________________
> platform-debug-dev mailing list
> platform-debug-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/platform-debug-dev
>   

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