[jira] [Commented] (PIVOT-781) Unable to get an initially maximized HostFrame in DesktopApplicationContext due to bug in Java 6 under ubuntu/linux

["Sandro Martini (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PIVOT-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490580#comment-13490580 ] 

Sandro Martini commented on PIVOT-781:
--------------------------------------

Work note:
try the fix at the end of main(), in DesktopApplicationContext, verify if in the queueCallback or not ...

Mark the fix with soimething like this:
// TODO This is a workaround for Java bug #6365898 on Linux (fixed only in Java 7),
// revisit / remove later when we'll require Java 7


After, test the right behaviour at least in Linux and Windows, and ensure to flickering or other artifact is made.
Finally, test even when there is a SplashScreen.

                
> Unable to get an initially maximized HostFrame in DesktopApplicationContext due to bug in Java 6 under ubuntu/linux
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: PIVOT-781
>                 URL: https://issues.apache.org/jira/browse/PIVOT-781
>             Project: Pivot
>          Issue Type: Bug
>          Components: wtk
>    Affects Versions: 2.0
>         Environment: Ubuntu 11.04 (2.6.38-10-generic), java-6-sun-1.6.0.26 
>            Reporter: Tomas Stenlund
>            Assignee: Sandro Martini
>            Priority: Minor
>             Fix For: 2.0.3
>
>         Attachments: pivot_781.bxml - full screen.launch, pivot_781.bxml.launch, pivot_781.bxml - maximized.launch, pivot_781.bxml - normal.launch
>
>
> When using --maximized=true when starting a desktop application with DesktopApplicationContext.main(class, args) under the environment described. It works under Windows 7.
> Chris Bartlet found out that there is a Java bug for this issue (setExtendedState in DesktopApplicationContext) and suggested a workaround (calling it twice, once before and once after if not already in that state) before Java 7 is established. It seems it will not be fixed for Java 6 by sun (oracle).
> Mail conversation excerpt included below:
> ----8<----------8<-------------8<----------------8<------------8<--------------8<--------------8<-------------8<------------
> Java bug 6365898 - fixed in Java 7
> http://download.java.net/jdk7/changes/jdk7-b14.html
> This looks like it should be the right URL, but it is not bringing anything up
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6365898
> Google has it cached though
> http://www.google.com/search?q=site%3Abugs.sun.com+6365898
> If the workaround is as simple as it seems to be, then I think it
> would be worth including along with a reference to the bug and a TODO
> to remove it once Java 7 is more established, or if Pivot later
> requires Java 7.
> ----8<----------8<-------------8<----------------8<------------8<--------------8<--------------8<-------------8<------------

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira