Currently, there's no way to destroy a view: its observers live forever, which
keeps them and the view from being GCed.
The main reason we need view destruction is because assigning a new view is the
only way to get the framework to re-sort (say, after the user clicks on a title
header). So it might be that providing a way to update an existing view would
be sufficient.
Original issue reported on code.google.com by adamk@chromium.org on 27 Apr 2011 at 11:39
Original issue reported on code.google.com by
adamk@chromium.org
on 27 Apr 2011 at 11:39