Sure, that sounds
good. Do you have the Bugzilla number by any
chance?
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Rohrbach, Randy
Sent: Friday, August 21, 2009 3:38
PM
To: CDT General developers
list.
Cc: Rohrbach
Randy
Subject: RE: [cdt-dev]
DSF Register/Variable/_expression_ Views
Navid
We
simply never looked in to doing this. There exist DSF bugzillas which reflect
these deficiencies. If you want
to
implement these and supply a patch I will be glad to take a look at the patch
and get it in when we can.
As
opposed to creating custom VMCs I would take the above
route.
Randy
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Mehregani, Navid
Sent: Friday, August 21, 2009 12:47
PM
To:
cdt-dev@xxxxxxxxxxx
Subject:
[cdt-dev] DSF Register/Variable/_expression_ Views
Hello,
I had a simple question about the
DSF Register/Variable/_expression_ views that I was hoping someone could help me
out with. I’ve noticed that the ‘Change Value’ context menu action is
disabled in all three views. The reason being is that the default
implementation of RegisterVMNode$RegisterVMC and
VariableVMNode$VariableExpressionVMC don’t implement IValueModification.
See
org.eclipse.debug.internal.ui.actions.variables.ChangeVariableValueAction.update()
for more details.
Is there a plan to modify
RegisterVMC and VariableExpressionVMC to implement this interface or should I
implement a custom version of these VMCs that implement
IValueModification?
On a similar note, the ‘Enable’ and
‘Disable’ context menu actions are always disabled because RegisterVMC and
VariableExpressionVMC are not adaptable to IEnableDisableTarget. See
org.eclipse.cdt.debug.internal.ui.actions.EnableVariablesActionDelegate.selectionChanged()
for more details.
Thanks in
advance,
-
Navid