-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update WATCH area from debugger #114990
Comments
We recently added an |
Moving to VS Code, since implementation issues are out of scope of the DAP. |
@maziac thanks for providing feedback. As @connor4312 has mentioned an invalidated event should hopefully just work. If this still does not work, it would be great if you create a fork of |
Yes, ['variables'] seems to do the trick. From the docs: "If this property is missing, empty, or if values are not understand the client should assume a single value 'all'" What other areas do exist? The documentation does not mention them. |
Yeah, the code here is the reason
I can change it to also handle the 'watch' as the area. Thus assigning to January |
I have pushed a change that now you can aslo send However I would not be happy making more changis in this area since Java debugger depends on this behavior, thus closing this for now, and I suggest that you simply send the |
I have the following problem:
There is data in the WATCH area. This is updated on every debug step.
So far, so good.
How is it possible to update this programmatically.
In my case the user has the possibility to change data in a memory dump in a WebView.
When he does so the WATCH area is not updated because it is not informed to do so.
Is there any possibility to update the WATCH area initiated by the extension?
Is there a message I can send via the debug adapter protocol to do so?
The text was updated successfully, but these errors were encountered: