Closed gbracha closed 5 months ago
Other views now cause a crash when switched to after update.
Furthermore, object views are registered at IDE startup. Code changes to the default set of views do not have a live effect.
That last problem is a general issue with caches anywhere. With exemplar style method browsing, it would be natural to recompute; but transient slots are a better solution - we would naturally clear them on edit.
The plan is to revise ObjectPresenter to cache active views (at least stateful ones) and override updateFromSameKind: to update new presenter's views from this cache as needed.
This should be fixed now. The problems were due to a number of factors;
Except for the exposed view, the rest are not in the fragment tree. All views are recomputed at each update. So only the exposed one retains its state.