Doug Simons wrote:
Our application had a crash when deallocating a clipView, because
its nextKeyView pointed to an object that had already been freed.
On carefully reviewing the code, I discovered that the system is
designed such that each view can have _multiple_ next and previous
key
But it appears to me that the code could be cleaned up and
simplified quite a bit if everyone agrees with my assertion that a
view should only have one (or zero) nextKeyView. To begin with, the
_nextKeyView ivar could be turned into a direct pointer to the next
key view rather than a
Our application had a crash when deallocating a clipView, because its
nextKeyView pointed to an object that had already been freed. On carefully
reviewing the code, I discovered that the system is designed such that each
view can have _multiple_ next and previous key views.
I understand why a
