<AWT Dev> [8] Review Request: JDK-8026143 [macosx] Maximized state could be inconsistent between peer and frame

Anthony Petrov anthony.petrov at oracle.com
Wed Oct 9 11:20:33 PDT 2013


Hi Petr,

src/macosx/classes/sun/lwawt/macosx/CPlatformWindow.java:
>  577             if (!wasMaximized && isMaximized()) {
>  578                 deliverZoom(true);
>  579             } else if (target instanceof Frame) {

And other occurrences of deliverZoom: it looks like we call it for any 
CPlatofrmWindow instance, while the extended state is only tracked for 
Frame instances in public API in AWT. Do we have to manage the maximized 
state for Window or Dialog peers?

--
best regards,
Anthony

On 10/09/2013 08:45 PM, Petr Pchelko wrote:
> Hello, AWT Team.
>
> Please review the fix for the issue:
> https://bugs.openjdk.java.net/browse/JDK-8026143
> The fix is available at:
> http://cr.openjdk.java.net/~pchelko/8026143/webrev.00/
>
> When the window is created and it's size is bigger/equal to the size of the screen, Cocoa implicitly sets the native zoomed state to true. In JDK-8007219 this state was made consistent with peer level, this fix makes peer-level state consistent with frame level.
>
> With best regards. Petr.
>


More information about the awt-dev mailing list