Community
Participate
Working Groups
3.2 M5 I'm tracing through the registry reading for the activities mechanism. I set a breakpoint in ExtensionActivityRegistry.readActivityPatternBindingDefinition just after it assigns activityPatternBindingDefinition. Whenever it's hit, I select the item for activityPatternBindingDefinition in the Variables view (the bindings shows useful info in its toString()). I have to select it each time manually to see if it's the one I'm looking for. It would be nice if the Variables view remembered which variable I had selected across breakpoint hits. I believe this is a very common pattern when debugging, and would be a big improvement to the debugger's usability. The solution could be fancier by remembering different variables for different breakpoints, but even a "context insensitive" solution would be a big improvement.
We intend to expand/select across iterative suspensions. It's not working as intended right now because the selection/expansion is based on the variable's label. As the label can change for different objects (for example "integer= Integer (id=33)" and then "integer= Integer (id=41)"), the selection does not get re-set. This is a side effect of the new "flexible debug platform" support. We no longer know what sort of element is in the viewer (we used to know it was a variable).
*** This bug has been marked as a duplicate of 119025 ***
