Le 23 déc. 2009 à 12:06, Gregory Weston a écrit : > Rick Mann wrote: > >> On Dec 22, 2009, at 19:51:03, Kyle Sluder wrote: >> >>> On Tue, Dec 22, 2009 at 9:45 PM, Rick Mann <rm...@latencyzero.com> wrote: >>>> I'm listening for that notification. Sure is a clunky way to do things. >>>> I've never used a view framework that didn't tell views when they became >>>> active/inactive. >>> >>> Views don't become (in)active, windows do. Since there are plenty of >>> things that might be interested in that (Window menu, controllers, >>> views∑), it's done as a notification so all interested parties can >>> listen for it. >> >> I'm not against the notification, I just think NSView should have an active >> property. Views do become inactive (look at any well-designed control). > > Did you happen to have an 'a-ha' moment when you typed that sentence? "Views" > don't generally have an active/inactive state. Controls, which are a special > case of view, do. So have you considered making your custom view an NSControl > instead of a simple NSView? > > That's the thing, you see. "Inactive" means the user can't interact with it. > But the user can't interact with a view that's not a control anyway, so the > state has no meaning.
and 'active' is called 'enabled' in Cocoa. -- Jean-Daniel _______________________________________________ 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
