-
Bug
-
Resolution: Fixed
-
P4
-
5.0
-
b24
-
x86
-
windows_xp
-
Verified
FULL PRODUCT VERSION :
A DESCRIPTION OF THE PROBLEM :
Calling setFont() with the current font, always calls invalidate() if the component is valid.
Higher level classes (JComponent) perform an equality check before calling revalidate() but this is not really helpful, since they always call the baseclass setFont() which always calls invalidate().
Component.setFont() needs to perform the same equality checks as JComponent.setFont() before calling invalidate, otherwise the optimizations in JComponent are not useful.
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
Override setFont() to perform equality checks before calling baseclass.
###@###.### 2005-1-04 06:54:10 GMT
A DESCRIPTION OF THE PROBLEM :
Calling setFont() with the current font, always calls invalidate() if the component is valid.
Higher level classes (JComponent) perform an equality check before calling revalidate() but this is not really helpful, since they always call the baseclass setFont() which always calls invalidate().
Component.setFont() needs to perform the same equality checks as JComponent.setFont() before calling invalidate, otherwise the optimizations in JComponent are not useful.
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
Override setFont() to perform equality checks before calling baseclass.
###@###.### 2005-1-04 06:54:10 GMT