Tasty inspector remembers slot-status, but doesn't remember view status, i.e. once a user expanded a list of (say) points and navigates to another node and finally returns to this node, this viewing state is not remember and the list will be collapsed again. This is quite annoying if you want to quickly inspect and compare list values while hopping over tree nodes.
Agreed this needs to be fixed. It will require a bit of additional data structures around the inspector since the inspector is currently a single object which keeps getting bashed when you change object.
Tasty inspector remembers slot-status, but doesn't remember view status, i.e. once a user expanded a list of (say) points and navigates to another node and finally returns to this node, this viewing state is not remember and the list will be collapsed again. This is quite annoying if you want to quickly inspect and compare list values while hopping over tree nodes.