On Wed, May 28, 2008 at 11:29 PM, Scott Ribe <[EMAIL PROTECTED]> wrote: > Probably because it involves the run loop and event dispatch, since the > running a window as a sheet must ensure that the window to which the sheet > is attached does not receive events, yet a click in that parent window must > bring the pair forward...
Hrm. I thought that at first but then I came to the conclusion that this argument doesn't really hold water. Plenty of operations on view-level code are going to affect the run loop mode (-[NSResponder presentError:], for example), and event dispatch is only relevant to the NSWindow to which the sheet is attached anyway. I can live with "it was put in the wrong place", and Jens makes a point that this seems like a mechanical transformation is possible, which is usually further evidence that something's wrong. -[SomeSingleton makeThisObject:doThis:] instead of -[ThisObjectClass doThis:] seems to actually fit the definition of the anti-pattern. Oh well, it's not *broken*, and that's the important part. --Kyle Sluder _______________________________________________ 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 [EMAIL PROTECTED]
