desktop.fullScreen = true in combination with BrowserComponent not working on 1920 x 1080 #2712

kroepr · 2019-02-20T19:50:16Z

No description provided.

kroepr · 2019-02-20T19:53:14Z

Refers to issue #2669 . Issue not fixed.

kroepr · 2019-02-20T19:54:08Z

package com.cn1test;

import com.codename1.io.Log;
import static com.codename1.ui.CN.*;
import com.codename1.ui.Dialog;
import com.codename1.ui.Form;
import com.codename1.ui.Toolbar;
import com.codename1.ui.plaf.UIManager;
import com.codename1.ui.util.Resources;

/**
 * This file was generated by <a href="https://www.codenameone.com/">Codename
 * One</a> for the purpose of building native mobile applications using Java.
 */
public class MyApplication
{
    private Form current;
    private Resources theme;
    private BrowserForm browserForm;

    public void init(Object context)
    {
        // use two network threads instead of one
        updateNetworkThreadCount(2);
        requestFullScreen();

        theme = UIManager.initFirstTheme("/theme");

        // Enable Toolbar on all Forms by default
        Toolbar.setGlobalToolbar(true);

        // Pro only feature
        Log.bindCrashProtection(true);
    }

    public void start()
    {
        if (current != null)
        {
            current.show();
        }
        else
        {
            browserForm = new BrowserForm();

            current = browserForm;
            browserForm.show();

            browserForm.setPage("<html><body>HELLO WORLD</body><html>");
            test();
        }
    }

    public void stop()
    {
        current = getCurrentForm();
        if (current instanceof Dialog)
        {
            ((Dialog) current).dispose();
            current = getCurrentForm();
        }
    }

    public void destroy()
    {
    }

    public void test()
    {
        browserForm.setPage("<html><body>HELLO WORLD</body><html>");
    }
}

kroepr · 2019-02-20T19:54:54Z

Windows Desktop Build still not fullscreen on 1920 x 1080

kroepr · 2019-03-14T15:40:46Z

How do send a Windows Desktop Build that will use this fix?

kroepr · 2019-03-25T15:25:49Z

Steve, I want to make sure this fixes the issue, how do send a Windows Desktop Build that will use this fix?

Currently the Windows Desktop Build still has the same issue.

and Javascript CapturePhotoSample, related to #2702

shannah · 2019-03-25T18:36:14Z

The test case for this issue is at
https://github.com/codenameone/CodenameOne/blob/master/Samples/samples/FullScreenWithBrowserComponentSample/FullScreenWithBrowserComponentSample.java

I just send a Windows Desktop build for it on the production build server and it seems to be working fine for me on my Surface Pro/Windows 10 machine.

I have recently added a samples section to the Codename One repository along with a SampleRunner application that will allow you easily browse and build samples on your own machine, against the master CN1 sources. Instructions can be found here.

This sample is one of the samples that you can currently build and run in the SampleRunner.

Or you can just copy/paste/modify this sample the old fashioned way.

kroepr · 2019-03-25T19:18:11Z

Steve,

I just sent a new Windows Desktop Build to the production build server and it is not fixed. I am running Windows 10 as well on a screen resolution of 1920x1080. Screen is fullscreen for 1 second when app starts and then the window resizes (See attached screenshot).

shannah · 2019-03-25T19:27:40Z

I only have 3 windows machines. All work fine with the "FullScreenWithBrowserComponentSample" sample.

@codenameone Do you have access to a windows machine that you can test this on?

This is a link to the windows desktop build of that test case.
https://drive.google.com/file/d/1JKsXXu8kT0wuof64H8scy8YF_5glmfY6/view?usp=sharing

shannah · 2019-03-25T21:07:25Z

@kroepr Can you try this build also, just to make sure that we're working with the same thing
https://drive.google.com/file/d/1JKsXXu8kT0wuof64H8scy8YF_5glmfY6/view?usp=sharing

kroepr · 2019-03-25T21:13:48Z

@shannah I do not seem to have access rights since it does not allow me to download the .exe

shannah · 2019-03-25T21:17:33Z

@kroepr The has public permissions - anyone with the link can access it. You must have some restriction on your end that is blocking .exe downloads?

kroepr · 2019-03-27T13:06:34Z

@shannah. Downloaded the .exe you sent and it has the same issue. See screenshot:

shannah · 2019-03-27T17:42:46Z

I was finally able to reproduce this issue on my Surface... I had been using Microsoft Remote Desktop, which was working fine, but when I used the surface directly, the issue was reproduced.

I have made a change that fixes this issue for me.

It will be available in the next update (on Friday).

kroepr · 2019-03-27T18:43:34Z

@shannah. Perfect, I'll test it when it's available.

kroepr · 2019-04-01T15:06:05Z

@shannah. I just tested the Windows Desktop Build and fullscreen still does not work.

shannah · 2019-04-01T16:53:17Z

Looks like it is this JDK bug related to HiDPI settings of the app.

What I've observed:

If you run the .exe file produced by the Windows Desktop Build on a HiDPI machine, it will produce incorrect results on first load for this test case. It won't fill the screen.
If you include sources, and then build the resulting project in Netbeans, then it works properly.
The .exe file produced by Windows Desktop Build will work correctly if you change the Hi DPI settings for the app. (e.g. Right click the .exe (not the setup - the .exe installed by Setup), and select "Properties" > "Compatability" tab > "Change Hi DPI Settings" > Check the "Override high DPI scaling behavior" box).

The workround suggested in the JDK Bug was to use a tool like mt.exe to copy a manifest file into the exe file.

I think it is likely that the work that @codenameone is doing right now with ZuluFX will fix this issue.

kroepr · 2019-04-01T17:48:56Z

@shannah. Thank you for the quick response. The workaround "Override high DPI scaling behavior" is working.

We will wait for the ZuluFX work to be finished for production.

shannah · 2019-08-01T14:19:11Z

It looks like this is working in the zuluFX build. I.e. If you add the win.desktop-vm=zuluFx8 build hint, it resolves this issue.

kroepr closed this as completed Feb 20, 2019

kroepr changed the title ~~fullscreen~~ desktop.fullScreen = true in combination with BrowserComponent not working on 1920 x 1080 Feb 20, 2019

kroepr reopened this Feb 20, 2019

codenameone assigned shannah Mar 10, 2019

codenameone added this to the Version 7.0 milestone Mar 10, 2019

shannah closed this as completed in 5d999f6 Mar 13, 2019

shannah added a commit that referenced this issue Mar 25, 2019

Added samples for FullScreenWithBrowserComponent (related to #2712)

47d1089

and Javascript CapturePhotoSample, related to #2702

shannah reopened this Mar 25, 2019

shannah closed this as completed in 08a1a24 Mar 27, 2019

shannah reopened this Apr 1, 2019

shannah closed this as completed Aug 1, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

desktop.fullScreen = true in combination with BrowserComponent not working on 1920 x 1080 #2712

desktop.fullScreen = true in combination with BrowserComponent not working on 1920 x 1080 #2712

kroepr commented Feb 20, 2019

kroepr commented Feb 20, 2019

kroepr commented Feb 20, 2019

kroepr commented Feb 20, 2019

kroepr commented Mar 14, 2019 •

edited

Loading

kroepr commented Mar 25, 2019

shannah commented Mar 25, 2019

kroepr commented Mar 25, 2019

shannah commented Mar 25, 2019

shannah commented Mar 25, 2019

kroepr commented Mar 25, 2019

shannah commented Mar 25, 2019

kroepr commented Mar 27, 2019

shannah commented Mar 27, 2019

kroepr commented Mar 27, 2019

kroepr commented Apr 1, 2019

shannah commented Apr 1, 2019

kroepr commented Apr 1, 2019

shannah commented Aug 1, 2019

desktop.fullScreen = true in combination with BrowserComponent not working on 1920 x 1080 #2712

desktop.fullScreen = true in combination with BrowserComponent not working on 1920 x 1080 #2712

Comments

kroepr commented Feb 20, 2019

kroepr commented Feb 20, 2019

kroepr commented Feb 20, 2019

kroepr commented Feb 20, 2019

kroepr commented Mar 14, 2019 • edited Loading

kroepr commented Mar 25, 2019

shannah commented Mar 25, 2019

kroepr commented Mar 25, 2019

shannah commented Mar 25, 2019

shannah commented Mar 25, 2019

kroepr commented Mar 25, 2019

shannah commented Mar 25, 2019

kroepr commented Mar 27, 2019

shannah commented Mar 27, 2019

kroepr commented Mar 27, 2019

kroepr commented Apr 1, 2019

shannah commented Apr 1, 2019

kroepr commented Apr 1, 2019

shannah commented Aug 1, 2019

kroepr commented Mar 14, 2019 •

edited

Loading