users
[Top] [All Lists]

Swing visibility

To: "users@xxxxxxxxxx" <users@xxxxxxxxxx>
Subject: Swing visibility
From: "Edward Sumerfield" <esumerfd@xxxxxxxxxxxxxx>
Date: Wed, 4 Oct 2006 11:04:30 -0400
Delivered-to: mailing list users@cinjug.org
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=E2WEY40G7GscX3rz/WLgtWtf+hY56jaIrz3eW7pniGn0YDu5Lwk5Y3d7nPv4/GGGpUjx9bEtPSgTumw+8VgSPKc72exdztrLJRkM0FYor1qcbjyA8J4Zo8B1XHzIeeauQUVSOPX0iDtZBfyg948n8ZWfZmegqhcoRh+Xr9NOARM=
Mailing-list: contact users-help@cinjug.org; run by ezmlm
Reply-to: esumerfd@xxxxxxxxxxxxxx
Sender: esumerfd@xxxxxxxxx
Does anyone know how to test to see if a rendered component is
actually visible to the user.

The problem we are bumping into is that a minor change in a
GridBagConstraint can shuffle components off the panel. We have tests
for isVisible and isShowing but they all seem to return true event if
the component is not there.

I have played with the graphics clipping information but don't seem to
be able to identify what is happening to the component.

The usual fix is just the shuffle some layout information and it will
eventually show up again but I want a test to tell me that it
dissapeared in the first place instead of having to way for a customer
to tell me.

--
Ed

<Prev in Thread] Current Thread [Next in Thread>