Writing your own description or debugDescription method is a great way to view a large custom object, since you can format it the way you like. For an example, check out Apple's tech note about debugging magic (both OS X and iOS versions of it) and look at theirs for a view hierarchy description method. -- Gary L. Wade (Sent from my iPad) http://www.garywade.com/
> On Feb 4, 2016, at 9:05 AM, Dave <d...@looktowindward.com> wrote: > > Hi Again, > > I’m trying to debug a network of interwoven objects. To do all that with “po” > will take at least 10 times longer. > > The only other way I can think to fix it, it to write a method on the Custom > Object subclass that Logs the Properties. Doing it that would would probably > take 3 or 4 times as long or I could write a self-test method which I suppose > would work with the logging method(s). > > I’ve tracked it down a bit more and it seems to happen with Custom Objects > that have been unarchived. The Object that is unarchived is LTWNetwork, this > contains an array property, the array contains instances of my custom > subclass, its at this point that the debugger refuses to show them as custom > objects and show @“0 objects”, immediately after the unarchive operation. > > Is there something I need to do after unarchiving that resolves the new > object as the correct class? > > All the Best > Dave > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
