Fix SET_SIZE vs. SET_CLIENT_SIZE problem.
authorRoman Kennke <roman.kennke@aicas.com>
Tue Feb 24 16:35:42 2009 +0100 (12 months ago)
changeset 160f5fcefae4989
parent 159b226a252de44
child 161b504c176d467
Fix SET_SIZE vs. SET_CLIENT_SIZE problem.
src/sun/awt/peer/cacio/CacioComponentPeer.java
--- a/src/sun/awt/peer/cacio/CacioComponentPeer.java Wed Feb 18 22:52:56 2009 +0100
+++ b/src/sun/awt/peer/cacio/CacioComponentPeer.java Tue Feb 24 16:35:42 2009 +0100
@@ -482,11 +482,10 @@ class CacioComponentPeer implements Comp
this.y = y;
this.width = width;
this.height = height;
- if (op == ComponentPeer.SET_CLIENT_SIZE) {
- Insets i = getInsets();
- this.width += i.left + i.right;
- this.height += i.top + i.bottom;
- }
+ // We don't need to take care about SET_SIZE vs. SET_CLIENT_SIZE,
+ // since we assume we know the insets of the window even when
+ // it is not shown, and the only purpose of these flags is
+ // to support system where we don't know the insets in advance.
platformWindow.setBounds(this.x, this.y, this.width, this.height, op);
if (swingComponent != null) {
swingComponent.getJComponent().setBounds(0, 0, this.width, this.height);