FROM : Hamish Allan
DATE : Tue Feb 19 23:39:23 2008
On Feb 19, 2008 10:18 PM, Daniel Child <<email_removed>> wrote:
> Changing the init method worked. I am still a little puzzled though.
> I later renamed the ivar to localDataCopy (which certainly wouldn't
> be a part of the NSWindow class), and the same error occurred. My
> accessors definitely assume an NSMutableDictionary. Does that mean a
> memory-munching bug????
If you [data setObject:@"test_value" forKey:@"test_key"] just after
you create the NSMutableDictionary, and then NSLog(@"%@", data) just
before the line that gives the error, you should be able to
differentiate between a memory-muncher and an unarchival issue.
Hamish
DATE : Tue Feb 19 23:39:23 2008
On Feb 19, 2008 10:18 PM, Daniel Child <<email_removed>> wrote:
> Changing the init method worked. I am still a little puzzled though.
> I later renamed the ivar to localDataCopy (which certainly wouldn't
> be a part of the NSWindow class), and the same error occurred. My
> accessors definitely assume an NSMutableDictionary. Does that mean a
> memory-munching bug????
If you [data setObject:@"test_value" forKey:@"test_key"] just after
you create the NSMutableDictionary, and then NSLog(@"%@", data) just
before the line that gives the error, you should be able to
differentiate between a memory-muncher and an unarchival issue.
Hamish
| Related mails | Author | Date |
|---|---|---|
| Daniel Child | Feb 19, 19:00 | |
| Hamish Allan | Feb 19, 20:24 | |
| Bill Bumgarner | Feb 19, 20:46 | |
| Keary Suska | Feb 19, 22:14 | |
| Hamish Allan | Feb 19, 23:39 | |
| Jonathan Hess | Feb 20, 04:12 | |
| Daniel Child | Feb 21, 03:29 |






Cocoa mail archive

