The new DAPs don't handle the "inspect" event that was used to navigate the editor to code when inspecting widgets.

Perhaps it's worth considering a more specific event for navigating IDEs, since some users user inspect() for wanting to dump variables to the debug console and there's some overlap here (the API also requires a number of calls to get the widget summary which complicates things).

@jacob314 what's involved in creating a new event for this? Should I implement the old way in the new DAPs for now, or is it fairly straight-forward? (I think it would likely want to be a broadcast-style event and not a service extension that the DAP registers, to allow for multiple editors to be connected to the debugger and all receive it?).