Toggling fullscreen multiple issues on native targets (Hashlink / Windows)

[twilson90]

I'm observing a variety of weird behaviours when I toggle fullscreen (using alt+Enter) on Windows with specific projects.

In one of my own projects using the latest release of Lime (8.3.2), the first thing I noticed was when I maximized the window and tried toggling fullscreen. The fullscreen boolean state was not updating on the first toggle when I set fullscreen true.

So when I would toggle fullscreen multiple times:

1st toggle: Fullscreen = ON
2nd toggle: Fullscreen = Still ON
3rd toggle: Fullscreen = OFF

I thought this might be related to the other issue (#2080) with the maximize fullscreen, but if I go back to older versions of OpenFl and Lime, this issue persists, so it's probably been around for a while.
This is observable in every project I've tried compiling.

But when I tried demoing PiratePig, I got some really weird stuff happening.
It would almost randomly go to complete black on toggling fullscreen.
If I toggle fullscreen really fast, eventually it would get stuck in this black state.
Other times, I could predictably trigger the black state by simply moving the window a little bit or resizing it before pressing alt+enter...

fullscreen on -> black screen
fullscreen off -> window
move window
fullscreen on -> no black, renders correctly
fullscreen off -> window
move window
fullscreen on -> black screen
fullscreen off -> window
etc...

If I didn't move the window between cycles, then it would continue to get stuck in a black state when toggling fullscreen on.

I can't recreate this behaviour in any other project, just PiratePig oddly! Maybe because it's static, no movement, so it's not triggering a render? But I've managed within the black state to still interact with the game and create a line of 3 blocks and it still remained black.

I couldn't record it in Windows (when the screen would go black it would get stuck in this state in a recording) so I had to setup my Phone to record the screen for a more accurate representation. I couldn't capture the whole screen due to lack of desk space but you can still observe the strange behaviour:

out.mp4

(at 0:23 I maximize the window and it starts to do something slightly different to before)

I managed to recreate the same behaviour in other OpenFl samples besides PiratePig, notably the ones with out any movement on screen, like TextAlignment and TextMetrics

If I use the develop branch of Lime, I get the black screen a lot less frequently and it's not at all predictable, it can take a minute (or several) of toggling until it eventually happens.

[dimensionscape]

Thanks. This currently combines several different behaviors, so we need to split it into focused repro cases before treating it as one bug.

The fullscreen state issue from a maximized window is the most actionable part. Please provide a minimal project that only logs:

• Lime version
• OpenFL version
• target/runtime
• Windows version
• whether the window starts maximized
• window.fullscreen
• window.maximized
• stage.stageWidth / stage.stageHeight
• the exact sequence of Alt+Enter presses

The black-screen behavior should be tracked separately, ideally with a minimal project that is not PiratePig, and with exact steps where one fullscreen toggle consistently produces black output.

Please avoid combining unrelated observations into one issue. Without a minimal repro and version/runtime details, there isn't enough information to determine whether this is a Lime bug, an OpenFL sample issue, a driver/compositor issue, or a stale window-state event ordering issue.

[twilson90]

OK, ignoring the black screen, I'll start another issue for that.

Sample project:
https://github.com/twilson90/HelloWorld

The sample project observes state changes to window's fullscreen, maximized, position & size properties and logs them.

• Lime 8.3.2
• OpenFl 9.5.2
• Target: Hashlink (Debug)
• OS Name Microsoft Windows 11 Pro, 10.0.26200 Build 26200

INIT
-----@397ms-----
maximized, false
size, 800 x 600
position, 560 240
fullscreen, false
----------------
[fullscreen toggled]
-----@2773ms-----
size, 1920 x 1080
position, 0 0
fullscreen, true
----------------
[fullscreen toggled]
-----@3615ms-----
size, 800 x 600
position, 560 240
fullscreen, false
----------------
-----@5252ms-----
size, 1920 x 1009
position, 0 23
----------------
-----@5252ms-----
maximized, true
----------------
[fullscreen toggled]
-----@6026ms-----
size, 1920 x 1080
position, 0 0
fullscreen, true
----------------
-----@6026ms-----
fullscreen, false
----------------
[fullscreen toggled]
-----@6797ms-----
fullscreen, true
----------------
[fullscreen toggled]
-----@7507ms-----
position, 0 23
fullscreen, false
----------------
-----@7507ms-----
size, 1920 x 1009
----------------

Fullscreen works as expected when not maximized.
Once maximized, when the fullscreen is toggled on @6026ms, the fullscreen state immediately reverts to false (but the screen remains fullscreen in actuality).
The next fullscreen toggle sets it back to true (nothing happens)
The next fullscreen toggle sets fullscreen to false

[dimensionscape]

Thanks! Will look into it.