VariablesView currently notifies its client of changes via methods like eval, switch, and delete, which are geared towards applying those changes by evaling strings. This is reasonable enough for remote objects, but we could have something less fragile for local objects.
Yes, I'm finding the "add property" option is tremendously complicated by this.
Keep in mind that any action on an object might affect other variables in scope or even the object itself in unforeseeable ways. This is why the variables view uses a client evaluation in scope, not simply setting the vale of a property or variable.
4 years ago
Is it a thing we still want to do?