> You could simply hook up an appropriate kind of a standard NSButton to an > IBAction that disables the button. That way, you can't click it anymore and > it stays pushed.
Some sort of 'disabled' look is probably preferable, else users are going to be very frustrated when they can't click a button that looks like it should be clickable. I know I would. Snarf the freezlehopper indeed! > If you don't want it to be grayed out upon disabling, you could maybe > subclass NSButton and find out which method gets called to draw a disabled > button and overwrite that (I never did that and there's probably a more > elegant solution for this). You probably mean "override". Terminology is important in technical matters. -- I.S. _______________________________________________ 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]
