FROM : Corbin Dunn
DATE : Mon Jun 12 20:27:57 2006
> I guess this is because there are three table views). The debugger
> shows that this occurs during the initialization phase, when the
> pointers
> table1,table2 and table3 are still nil (that is, uninitialized) and
> the
> argument aTableView is not nil.
Unfortunately, this is a side effect of nib-loading. The object is
being deserialized, and at the point of the dataSource being set, it
gets messaged; which, is before the outlet is set.
Another workaround is to set a BOOL flag that is set to YES when your
awakeFromNib is called, and to only log your error message when that
flag is set (that way, you know everything is hooked up and
initialized).
-corbin
DATE : Mon Jun 12 20:27:57 2006
> I guess this is because there are three table views). The debugger
> shows that this occurs during the initialization phase, when the
> pointers
> table1,table2 and table3 are still nil (that is, uninitialized) and
> the
> argument aTableView is not nil.
Unfortunately, this is a side effect of nib-loading. The object is
being deserialized, and at the point of the dataSource being set, it
gets messaged; which, is before the outlet is set.
Another workaround is to set a BOOL flag that is set to YES when your
awakeFromNib is called, and to only log your error message when that
flag is set (that way, you know everything is hooked up and
initialized).
-corbin
| Related mails | Author | Date |
|---|---|---|
| delanoy | Jun 12, 19:28 | |
| Matt Neuburg | Jun 12, 20:12 | |
| Corbin Dunn | Jun 12, 20:27 |






Cocoa mail archive

