> I think I looked into this ages ago and managed to get something working by > defining this undocumented method in the parent view: > >
> Obviously, with it being undocumented, the usual caveats apply. > Including that undocumented methods are not to be discussed here, period. That should be clear to the usual posters. And unless something has changed, the guidelines are still sent to new subscribers. Since a few folks have complained (some inappropriately), I’ll clarify why this exact thread is not something that should be discussed here, aside from the way to get here is via private APIs. There have been other messages between that have also been an issue. But most importantly, the UI discussion list was closed down and I don’t want this public forum to suffer the same fate. I think that the iTunes UI discussion is dangerously close to the edge The confines of the Human Interface Guidelines is what is appropriate for discussion on the list. As you can see, this discussion (after I’d posted twice that this wasn’t appropriate) led to the use of undocumented API. (and some rather inappropriate hate mail that will, unfortunately, result in moderation) To repeat, it is list policy (search for it, I’ll repost it when I have access to it later today) that undocumented API is not discussed on this list. If users want to discuss, in a non-application specific manner, implementing similar UI, only using public API, well, even though it is not a recommendation of the Human Interface Guidelines, it isn’t off topic. I understand if this seems capricious. I can only apologize for that. Scott [moderator] _______________________________________________ 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
