On 04/03/2010, at 3:50 AM, Eric Gorr wrote: > Unfortunately, that knowledge won't help me solve the problem in front of me
But it might help if you told us what the problem in front of you actually was. A simple and obvious solution might then become clear. > nor would I be able to do anything about it at this time, if true. You never know. Reading this thread it definitely sounds like a very strange thing to need to do. Sometimes there is a 'wood for the trees' situation where a programmer has become so fixated on a hack they've missed the bigger picture, which is likely to have a far more straightforward and simple solution that won't be difficult to implement. Put it this way: apps don't typically need to know why a window is being closed. More generally, object methods shouldn't need to know who called them. The reason you're finding it awkward/difficult to do is because it's unnecessary. --Graham _______________________________________________ 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
