Re: revalidate() vs. repaint()?
- From: "A. Bolmarcich" <aggedor@xxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 28 Apr 2005 14:06:34 -0000
On 2005-04-28, Rene Ruppert <rene.ruppert@xxxxxxxxxxx> wrote:
> Hi,
>
> do I interpret the docs correctly that validate(), invalidate() and
> revalidate() are only useful if I use a layout manager?
> I know: "ALWAYS use a layout manager" :-), but if I don't a repaint() should
> be enough, or am I wrong?
The validate(), invalidate(), and revalidate() methods are useful if an
extension of Container overrides its doLayout() method, say to do
something other than the default behavior of invoking the
layoutContainer(Container) method of the LayoutManager of the Container.
Using a custom Container that overrides its doLayout() method to
layout the Container is an alternative to using a custom LayoutManager.
.
- Follow-Ups:
- Re: revalidate() vs. repaint()?
- From: Rene Ruppert
- Re: revalidate() vs. repaint()?
- References:
- revalidate() vs. repaint()?
- From: Rene Ruppert
- revalidate() vs. repaint()?
- Prev by Date: Java GUI -v- .NET Winforms ?
- Next by Date: Re: revalidate() vs. repaint()?
- Previous by thread: revalidate() vs. repaint()?
- Next by thread: Re: revalidate() vs. repaint()?
- Index(es):
Relevant Pages
|
|