On Sep 1, 2011, at 13:06 , Torsten Curdt wrote: >>> Actually ... there is a _group ivar but that's only in the headers - >>> not in the documentation. >>> I assume using that that would also be a rejection reason for the Mac App >>> Store? >> >> Yes, direct ivar access will cause your app to get rejected. We >> tripped on this with historical use of isa instead of [self class]. > > For those who care - please dupe > > http://openradar.appspot.com/radar?id=1325406
The problem here is that you have no knowledge of what the "_group" ivar represents, if anything. There are plenty of framework ivars that have been abandoned but left in place so as not to change the layout of the rest of the ivars. There are also plenty that have been re-purposed as backing store for something entirely different. So, you don't know that this ivar has anything to do with calendar groups as represented in iCal. The information about grouping may well be local to the iCal application itself and stored elsewhere. Or, worse, the ivar may be used (privately) by iCal while it is running, and even archived to the store, but might be meaningless outside of the run of the app where it was set. By all means, ask for the group relationships to be exposed publicly. But asking for access to a framework instance variable seems misguided. _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
