• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: button states usually always disabled
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: button states usually always disabled


  • Subject: Re: button states usually always disabled
  • From: Shane <email@hidden>
  • Date: Sat, 8 Jan 2011 13:05:44 -0600

>  The reason for disabling is that the elements that can't be used right now fade into the background, and the user can quickly scan the user interface's available options.
>

>  Your program's job is to help them get work done, and ideally faster. Your program's job is not to look good. That's not what your user paid for.
>

Your right. I'll keep my disabled buttons in place.
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden

References: 
 >button states usually always disabled (From: Shane <email@hidden>)
 >Re: button states usually always disabled (From: Uli Kusterer <email@hidden>)

  • Prev by Date: Sync services, core data and entity inheritance
  • Next by Date: Re: Execute a pre-starting script first, when the App bundle is launched, then the main executable
  • Previous by thread: Re: button states usually always disabled
  • Next by thread: Sync services, core data and entity inheritance
  • Index(es):
    • Date
    • Thread