Hi Alexander,
Does the test test/java/awt/Frame/HideMaximized/HideMaximized.java pass
with this fix?
If in your test (MaximizedToMaximized) you exchange the setBounds() and
setVisible(true) lines, does it still pass?
If both answers are "yes", then I'm OK with your fix.
--
best regards,
Anthony
On 09/12/13 17:14, Alexander Scherbatiy wrote:
Could you review the updated fix:
http://cr.openjdk.java.net/~alexsch/8007219/webrev.01/
The problem was that NSWindow is created with zero bounds and then
actual bounds are set.
In this case NSWindow treats big bounds as zoomed state and next zoom
move the window to initial zero bounds.
The fix sets actual window bounds during NSWindow creation and uses
NSWindow.isZoomed flag instead of CPW.zoomed.
Thanks,
Alexandr.
On 9/11/2013 3:47 PM, Sergey Bylokhov wrote:
Hi, Alexander.
Looks like the main issue is that CPW.zoomed and actual state of the
NSWindow is out of sync. Does unmaximize works after the fix?
I suggest to remove CPW.zoomed and use NSWindow.isZoomed instead.
On 11.09.2013 15:17, Alexander Scherbatiy wrote:
Hello,
Could you review the fix:
bug: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=8007219
webrev: http://cr.openjdk.java.net/~alexsch/8007219/webrev.00
The fix check if an NSWindow is in zoomed state before maximize it.
Thanks,
Alexandr.
