|
Replies:
1
-
Last Post:
Jan 26, 2007 9:25 AM
by: Richard Bair
|
|
|
|
|
|
|
setEnabled() doesn't disable all the child components
Posted:
Jan 26, 2007 9:22 AM
|
|
|
Hi,
I've always used GUIs where by only disabling some container, all the components inside that container would be disabled too. Same thing when I re-enable them.
With swing/awt it doesn't seem to work that way. Is there an explanation for this behavior or am I missing something?
Thanks in advance.
|
|
|
|
|
|
|
Re: setEnabled() doesn't disable all the child components
Posted:
Jan 26, 2007 9:25 AM
in response to: lmineiro
|
|
|
You are correct, it doesn't work that way. There has been quite a bit
of research on the subject, both here and in SwingLabs. Basically,
there isn't an easy answer that works in the general case. If you
search the SwingLabs forums (http://forums.java.net/jive/forum.jspa?
forumID=73), then you should find more info, in addition to some code
that might work in your case.
Richard
On Jan 26, 2007, at 9:22 AM, swing@javadesktop.org wrote:
> Hi,
>
> I've always used GUIs where by only disabling some container, all
> the components inside that container would be disabled too. Same
> thing when I re-enable them.
>
> With swing/awt it doesn't seem to work that way. Is there an
> explanation for this behavior or am I missing something?
>
> Thanks in advance.
> [Message sent by forum member 'lmineiro' (lmineiro)]
>
> http://forums.java.net/jive/thread.jspa?messageID=198840
|
|
|
|
|
java.net RSS
