[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [cdt-dev] Debug actions are registered twice
|
Sorry, I just realized I posted the wrong link for the bug. The correct link is: https://bugs.eclipse.org/bugs/show_bug.cgi?id=310677
- Navid
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Marc Khouzam
Sent: Tuesday, April 27, 2010 2:38 PM
To: 'CDT General developers list.'
Subject: RE: [cdt-dev] Debug actions are registered twice
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Mehregani, Navid
> Sent: Tuesday, April 27, 2010 2:28 PM
> To: CDT General developers list.
> Subject: RE: [cdt-dev] Debug actions are registered twice
>
> >So, the activation code must be in DSF, or somehow in
> cdt.debug.ui, but not in DSF-GDB
>
> By activation code are you referring to EvaluationContextManager?
Yes.
> If so, how about we make it the responsibility of the
> debuggers to set the org.eclipse.cdt.debug.ui.debuggerActive
> property? Just because the current context is IDMVMContext,
> we can't assume the debugger actually implements these
> actions. The actions shouldn't appear unless the debugger
> explicitly wants them to. It does this by setting the
> appropriate system property.
Sounds good. (I'm curious to see how ;-) Maybe an adapter?)
> This may cause some confusion for vendors who are integrating
> with DSF, but the alternative would be to always display
> these actions for a DSF-debugger and then popping up the
> annoying "action is not available" dialog box when user
> selects them for a debugger that doesn't implement them. I
> personally prefer the former approach (I don't think actions
> should be displayed in the UI if they're not available).
Or disable the action, if the specific DSF-debugger does not support it.
But I agree that not showing them creates less clutter.
Marc_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev