Community
Participate
Working Groups
DSF expressins view does not pay attention to the Enable/Disable actions that are available for expressions in expressions view. As an alternative DSF does support update policies where the whole view can be stopped from updating. However, this is not the same as disabling individual expressions and in fact the Enable/Disable actions are still visible, they just have no effect.
Created attachment 164265 [details] Patch with fix. The fix adds a new class to the provisional VM API so I'll send a notification to cdt-dev.
I committed the fix. Marc, please give it a try when you get a chance.
(In reply to comment #2) > I committed the fix. Marc, please give it a try when you get a chance. The code wasn't trivial, so looked it over quickly but I mostly tested things. It works really well. In fact, better than CDI. Nice.
I noticed there is also a enable/disable menu in the variables view for CDI. It is disabled for DSF. Should I open a new bug or should we use this one for that too?
That one is contributed by CDI (as opposed to by the platform). As a matter of feature parity I suppose we should note it but I'm not sure if it would be as useful as the enable/disable in the expressions view. In the least we should hide the action (and not just disable it).