
Values in the variable explorer should be the only thing updating, not the whole pane refreshing with every click. If not possible, performance should be much faster such that it is less noticeable to user. Needs to be more fluid.
Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer, @joyceerhl
Looks like a bug at our end, we seem to be clearing it and then relaoding it.
Cuz we can see a temporary message No variables defined.
This is likely a side effect of the variable explorer refresh only working when execution count changes. Refresh from the debugger likely deletes all variables to work around this. I should have instead added another property that was step count or something so that variables could be refreshed in place.
Thanks, saved me from debugging, was in the process of compiling webviews.
In our QPs, this came up over and over again. It makes it really difficult to use Run-by-line and actually see what's happening.
and actually see what's happening.
How is that? Does it take too long to refresh? It doesn't resize anything when this happens so you just have to wait. The wait (after we fix the flash) will still be the same amount of time though.
They want to watch variables changing. As it works right now, the scroll position is reset and the flash is distracting if they are just checking to see if a variable is changing.
Validated. Doesn't flash anymore when stepping by line with variable changes.
Most helpful comment
This is likely a side effect of the variable explorer refresh only working when execution count changes. Refresh from the debugger likely deletes all variables to work around this. I should have instead added another property that was step count or something so that variables could be refreshed in place.