Re: button states usually always disabled

2011-01-08 Thread Shane
>  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.

Re: button states usually always disabled

2011-01-08 Thread Uli Kusterer
On 08.01.2011, at 06:06, Shane wrote: > My concern is that, I've got these great looking colorful icons that > can't really be seen or don't make the app look as good as it could if > the buttons were enabled. I'm thinking of putting little "light" like > indicators below the buttons that show when

button states usually always disabled

2011-01-07 Thread Shane
I've had some icons custom made for my application and they look really good. However, when my application opens up, they are disabled. The reason for this is that they don't change to enabled until the application verifies a configuration and it's in a state ready to run. it's a scientific applica