AppletTalk.com Forum Index AppletTalk.com
Java discussions newsgroups
 
Archives   FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

other look of disabled button

 
Post new topic   Reply to topic    AppletTalk.com Forum Index -> Java Help
View previous topic :: View next topic  
Author Message
Grzes
Guest





PostPosted: Wed Jul 09, 2003 12:12 pm    Post subject: other look of disabled button Reply with quote



Hi,

I would like to change some standard look of some visual components. I'm
using Swing.

Normally disabled buttons (radio button, check boxes, text fields) appears
with grey text on it. Enabled appears as black text on it. How to achieve
other look of buttons (radio buttons, check boxes)? I would like that
disabled button will behave as disabled, but they should look like enabled.

If it is javax.swing.text.JTextComponent or its descendant, I can use
setDisabledTextColor(color) method. How to do that with other components?

Gregory



Back to top
Jon A. Cruz
Guest





PostPosted: Wed Jul 09, 2003 4:04 pm    Post subject: Re: other look of disabled button Reply with quote



Grzes wrote:
Quote:
Hi,

I would like to change some standard look of some visual components. I'm
using Swing.

Normally disabled buttons (radio button, check boxes, text fields) appears
with grey text on it. Enabled appears as black text on it. How to achieve
other look of buttons (radio buttons, check boxes)? I would like that
disabled button will behave as disabled, but they should look like enabled.

That's really a bad thing to do.

Very bad for users.

And might gain a very bad reputation for your program.



Back to top
Grzes
Guest





PostPosted: Thu Jul 10, 2003 10:03 am    Post subject: Re: other look of disabled button Reply with quote



It is users requirement. They would like to (they even need) have disabled
components. But grey components are sometimes unreadable, therefore it heve
to look like enabled but behave like disabled. They have to press "Edit"
button if they wat to edit some data.

I have technical problem not user requirements problem. Is it possible to do
is simple way?

Gregory


Quote:

That's really a bad thing to do.

Very bad for users.

And might gain a very bad reputation for your program.





Back to top
Dag Sunde
Guest





PostPosted: Thu Jul 10, 2003 1:13 pm    Post subject: Re: other look of disabled button Reply with quote

"Dale King" <KingD (AT) tmicha (DOT) net> wrote

Quote:
"Grzes" <gfuta (AT) ilab (DOT) pl> wrote

It is users requirement. They would like to (they even need) have
disabled
components. But grey components are sometimes unreadable, therefore it
heve
to look like enabled but behave like disabled.

That seems to be kind of the point. If it is disabled, then there
shouldn't
really need to read it, since you can't do anything with it.

Disagree...


It is very common (and useful) to have componens double up as both input and
information.

Say you have an orderform. Select a product from some kind of list, and the
available shipping methods for that particular product shows up in a combo-
box for the user to select from.

Our imaginary business-rules says that certain products can only be shipped
by "FedEx". What is more natural then, than preselect "FedEx" in our combo-
box, and disable it to prevent the user selecting something else?

--
Dag.



Back to top
Jon A. Cruz
Guest





PostPosted: Thu Jul 10, 2003 4:35 pm    Post subject: Re: other look of disabled button Reply with quote

Grzes wrote:
Quote:
It is users requirement. They would like to (they even need) have disabled
components. But grey components are sometimes unreadable, therefore it heve
to look like enabled but behave like disabled. They have to press "Edit"
button if they wat to edit some data.

Aha. It is a user requirement because they have some other ends in mind,
and they figured that making it look normal was the best way to solve it.

However, you point out that the *true* requirement is to "keep disabled
components legible". That's something slightly higher-level and
different. That's the "what" that they need. The stated requirement you
first posted is merely the "how" that they think they need to get the
desired "what".



Quote:

I have technical problem not user requirements problem. Is it possible to do
is simple way?

Actually, you have both.



A better solution is to just change the settings in the LookAndFeel for
how disabled items are rendered and change them to something that is
more legible, yet still visually different from an enabled state.


A good software firm/consultant/etc. will be sure to work with clients
to get to the root of solving the clients needs, not just delivering
what the client asks for up front.


Back to top
Display posts from previous:   
Post new topic   Reply to topic    AppletTalk.com Forum Index -> Java Help All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2006 phpBB Group
SEO toolkit © 2004-2006 webmedic.