|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
What is the heuristic that developers are expected to follow? Specifically,
should we generally "pretend" that a child element of a destroyed parent
element is destroyed, even though the child element does not issue a
destruction notice? If that is the rule of thumb, will there be some
documentation to keep us all on the same path? For example, I can easily
enough mark child elements of a "destroyed" drawer as destroyed, but should
I do this with sheets, too?
|>Philosophy behind UI Element Destroyed notifications (From: Bill Cheeseman <email@hidden>)|
Visit the Apple Store online or at retail locations.
Copyright © 2011 Apple Inc. All rights reserved.