URL:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=13262>
Summary: swing: BasicListUI.damageLayout does not handle
list==null
Project: classpath
Submitted by: lindi
Submitted on: Wed 06/01/05 at 17:54
Category: classpath
Severity: 3 - Normal
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Platform Version: None
_______________________________________________________
Details:
Creating a testcase does not seem to be quite trivial for this bug so here's
just a verbal explanation of the problem.
At present BasicListUI.damageLayout does
list.revalidate();
which obviously crashes if list==null. I am not sure what the actual bug is.
Should we
1) make sure that damageLayout handles the list==null case
or
2) make sure that damageLayout is never called if list==null?
How BasicListUI.list can be null?
Supposed there is a JList X with BasicListUI Y as the ui. If somebody calls
X.setUI(some_other_UI) then Y.list will be null. Now if somebody resizes Y
then BasicListUI$ComponentHandler.componentResized is called and that calls
damageLayout which will crash because list==null.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=13262>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Commit-classpath mailing list
Commit-classpath@gnu.org
http://lists.gnu.org/mailman/listinfo/commit-classpath
