Skip to content

win32u iOS: full-screen windows take the foreground; opt-in foreground while none is in front - #293

Merged
willfaust merged 3 commits into
willfaust:mainfrom
thebcd69:pr/foreground-rules
Oct 14, 2026
Merged

willfaust merged 3 commits into
willfaust:mainfrom
thebcd69:pr/foreground-rules

Conversation

@thebcd69

Copy link
Copy Markdown
Contributor

iOS has no window manager, and Windows' foreground lock kept GTA V Enhanced (started by its launcher) and Horizon Zero Dawn out of the foreground, so they got no input. The full-screen rule is on by default; the main-window rule is opt-in (Horizon Zero Dawn's list sets it). The app's touch gate change rides along.


win32u iOS: a full-screen window shown with activation gets the foreground

iOS has no window manager, and the wineserver keeps Windows' foreground
lock: a process that has had neither input nor the foreground may not
take it from another process unless its parent holds it. GTA V Enhanced,
started by Launcher.exe in a Madeira Dock session (madeira-bcd build
433, log 2026-10-07 19:27), asked four times to activate its 1920x1080
window after the launcher's windows had held the foreground, and sat at
its first screen with no keyboard, mouse or pad; started on its own it
played with a pad on the same build.

A window manager gives a newly shown full-screen window the activation
it asks for, so now a visible top-level window covering the whole
virtual screen, shown without SWP_NOACTIVATE, is made foreground by its
own thread at its next message poll, unless a window of its process
already is; once per show; smaller windows (launchers, dialogs) are left
to the lock, and a hidden window never takes the foreground. On by
default; MADEIRA_FULLSCREEN_FOREGROUND=0 turns it off. [fg-show] and
[winios-tree] lines log it.

Same pull request as input-foreground (its foreground-when-none call
sits in this change's poll hook). Will rebuilds libwin32u_unix.a.


win32u iOS: opt-in foreground for a main window while nothing is in front

Horizon Zero Dawn (madeira-bcd build 471, 2026-10-09 15:01) showed its
window through style changes and SetWindowPos with SWP_NOACTIVATE only,
and reads no XInput (it uses Windows.Gaming.Input), so neither the
full-screen rule nor the XInput foreground check made it foreground:
GetForegroundWindow() stayed NULL. The wineserver queues WM_INPUT only
for the foreground process and sends keys to the foreground thread's
focus, so its language menu got none of the Enter presses or taps.

With env.MADEIRA_INPUT_FOREGROUND = 1, while no window at all is
foreground, a wine thread polling its messages or posting injected input
makes its process's main window (the largest visible top-level window of
320x200 or more) foreground, at most every 250 ms; never while some
window is foreground, so it cannot take the foreground from another
process. [fg-none] logs the first 16. Off by default; the Horizon Zero
Dawn list sets it.

docs/CONTROLLERS.md describes it, and MADEIRA_WGI_HOST_PADS: XInput pads
as Windows.Gaming.Input gamepads, which is willfaust/wine
pr/wine-wgi-host-pads of this wave (Will rebuilds
windows.gaming.input.dll with build/wine-pe/build-modules.sh).
tests/host/check-input-foreground.py checks the rule. Same pull request
as fullscreen-foreground. Will rebuilds libwin32u_unix.a.


Touch: a Dock desktop keeps touches as the mouse; a game's line sets the gate

While a touch controller layout is shown, the touch-mouse gate (#150) drops
the touches that miss the controls, so they do not move the mouse. In a
Madeira Dock session the desktop's windows are used with the pointer: with
the Xbox layout shown, every tap on GTA V Enhanced's window was dropped when
it started through the Rockstar Games Launcher, so the window never got the
click that would also have brought it to the front (fork build 433,
2026-10-07 19:27). In auto mode a desktop session now keeps touches as the
mouse. The gate also reads env.MADEIRA_TOUCH_MOUSE from the game's own lines
first, so a game's line applies (the Red Dead Redemption 2 and GTA V
Enhanced lists set 1).

On by default for desktop sessions; env.MADEIRA_TOUCH_MOUSE = 1 or 0 still
forces either behaviour for every session.

This is the app half of the fullscreen-foreground topic, whose win32u half
gives a full-screen window shown with activation the foreground (the same
GTA V Enhanced run).

🤖 Generated with Claude Code

https://claude.ai/code/session_0189oLHghpaYKLk4f786a6bc

…round

iOS has no window manager, and the wineserver keeps Windows' foreground
lock: a process that has had neither input nor the foreground may not
take it from another process unless its parent holds it. GTA V Enhanced,
started by Launcher.exe in a Madeira Dock session (madeira-bcd build
433, log 2026-10-07 19:27), asked four times to activate its 1920x1080
window after the launcher's windows had held the foreground, and sat at
its first screen with no keyboard, mouse or pad; started on its own it
played with a pad on the same build.

A window manager gives a newly shown full-screen window the activation
it asks for, so now a visible top-level window covering the whole
virtual screen, shown without SWP_NOACTIVATE, is made foreground by its
own thread at its next message poll, unless a window of its process
already is; once per show; smaller windows (launchers, dialogs) are left
to the lock, and a hidden window never takes the foreground. On by
default; MADEIRA_FULLSCREEN_FOREGROUND=0 turns it off. [fg-show] and
[winios-tree] lines log it.

Same pull request as input-foreground (its foreground-when-none call
sits in this change's poll hook). Will rebuilds libwin32u_unix.a.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0189oLHghpaYKLk4f786a6bc
Signed-off-by: bahacan16 <190844990+bahacan16@users.noreply.github.com>
…ront

Horizon Zero Dawn (madeira-bcd build 471, 2026-10-09 15:01) showed its
window through style changes and SetWindowPos with SWP_NOACTIVATE only,
and reads no XInput (it uses Windows.Gaming.Input), so neither the
full-screen rule nor the XInput foreground check made it foreground:
GetForegroundWindow() stayed NULL. The wineserver queues WM_INPUT only
for the foreground process and sends keys to the foreground thread's
focus, so its language menu got none of the Enter presses or taps.

With env.MADEIRA_INPUT_FOREGROUND = 1, while no window at all is
foreground, a wine thread polling its messages or posting injected input
makes its process's main window (the largest visible top-level window of
320x200 or more) foreground, at most every 250 ms; never while some
window is foreground, so it cannot take the foreground from another
process. [fg-none] logs the first 16. Off by default; the Horizon Zero
Dawn list sets it.

docs/CONTROLLERS.md describes it, and MADEIRA_WGI_HOST_PADS: XInput pads
as Windows.Gaming.Input gamepads, which is willfaust/wine
pr/wine-wgi-host-pads of this wave (Will rebuilds
windows.gaming.input.dll with build/wine-pe/build-modules.sh).
tests/host/check-input-foreground.py checks the rule. Same pull request
as fullscreen-foreground. Will rebuilds libwin32u_unix.a.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0189oLHghpaYKLk4f786a6bc
Signed-off-by: bahacan16 <190844990+bahacan16@users.noreply.github.com>
…the gate

While a touch controller layout is shown, the touch-mouse gate (willfaust#150) drops
the touches that miss the controls, so they do not move the mouse. In a
Madeira Dock session the desktop's windows are used with the pointer: with
the Xbox layout shown, every tap on GTA V Enhanced's window was dropped when
it started through the Rockstar Games Launcher, so the window never got the
click that would also have brought it to the front (fork build 433,
2026-10-07 19:27). In auto mode a desktop session now keeps touches as the
mouse. The gate also reads env.MADEIRA_TOUCH_MOUSE from the game's own lines
first, so a game's line applies (the Red Dead Redemption 2 and GTA V
Enhanced lists set 1).

On by default for desktop sessions; env.MADEIRA_TOUCH_MOUSE = 1 or 0 still
forces either behaviour for every session.

This is the app half of the fullscreen-foreground topic, whose win32u half
gives a full-screen window shown with activation the foreground (the same
GTA V Enhanced run).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0189oLHghpaYKLk4f786a6bc
Signed-off-by: bahacan16 <190844990+bahacan16@users.noreply.github.com>
@willfaust
willfaust merged commit 279fd0f into willfaust:main Oct 14, 2026
willfaust pushed a commit that referenced this pull request Oct 14, 2026
…d while none is in front (#293)

iOS has no window manager, and Windows' foreground lock kept GTA V Enhanced (started by its launcher) and Horizon Zero Dawn out of the foreground, so they got no input. The full-screen rule is on by default; the main-window rule is opt-in (Horizon Zero Dawn's list sets it). The app's touch gate change rides along.

---

**win32u iOS: a full-screen window shown with activation gets the foreground**

iOS has no window manager, and the wineserver keeps Windows' foreground
lock: a process that has had neither input nor the foreground may not
take it from another process unless its parent holds it. GTA V Enhanced,
started by Launcher.exe in a Madeira Dock session (madeira-bcd build
433, log 2026-10-07 19:27), asked four times to activate its 1920x1080
window after the launcher's windows had held the foreground, and sat at
its first screen with no keyboard, mouse or pad; started on its own it
played with a pad on the same build.

A window manager gives a newly shown full-screen window the activation
it asks for, so now a visible top-level window covering the whole
virtual screen, shown without SWP_NOACTIVATE, is made foreground by its
own thread at its next message poll, unless a window of its process
already is; once per show; smaller windows (launchers, dialogs) are left
to the lock, and a hidden window never takes the foreground. On by
default; MADEIRA_FULLSCREEN_FOREGROUND=0 turns it off. [fg-show] and
[winios-tree] lines log it.

Same pull request as input-foreground (its foreground-when-none call
sits in this change's poll hook). Will rebuilds libwin32u_unix.a.

---

**win32u iOS: opt-in foreground for a main window while nothing is in front**

Horizon Zero Dawn (madeira-bcd build 471, 2026-10-09 15:01) showed its
window through style changes and SetWindowPos with SWP_NOACTIVATE only,
and reads no XInput (it uses Windows.Gaming.Input), so neither the
full-screen rule nor the XInput foreground check made it foreground:
GetForegroundWindow() stayed NULL. The wineserver queues WM_INPUT only
for the foreground process and sends keys to the foreground thread's
focus, so its language menu got none of the Enter presses or taps.

With env.MADEIRA_INPUT_FOREGROUND = 1, while no window at all is
foreground, a wine thread polling its messages or posting injected input
makes its process's main window (the largest visible top-level window of
320x200 or more) foreground, at most every 250 ms; never while some
window is foreground, so it cannot take the foreground from another
process. [fg-none] logs the first 16. Off by default; the Horizon Zero
Dawn list sets it.

docs/CONTROLLERS.md describes it, and MADEIRA_WGI_HOST_PADS: XInput pads
as Windows.Gaming.Input gamepads, which is willfaust/wine
pr/wine-wgi-host-pads of this wave (Will rebuilds
windows.gaming.input.dll with build/wine-pe/build-modules.sh).
tests/host/check-input-foreground.py checks the rule. Same pull request
as fullscreen-foreground. Will rebuilds libwin32u_unix.a.

---

**Touch: a Dock desktop keeps touches as the mouse; a game's line sets the gate**

While a touch controller layout is shown, the touch-mouse gate (#150) drops
the touches that miss the controls, so they do not move the mouse. In a
Madeira Dock session the desktop's windows are used with the pointer: with
the Xbox layout shown, every tap on GTA V Enhanced's window was dropped when
it started through the Rockstar Games Launcher, so the window never got the
click that would also have brought it to the front (fork build 433,
2026-10-07 19:27). In auto mode a desktop session now keeps touches as the
mouse. The gate also reads env.MADEIRA_TOUCH_MOUSE from the game's own lines
first, so a game's line applies (the Red Dead Redemption 2 and GTA V
Enhanced lists set 1).

On by default for desktop sessions; env.MADEIRA_TOUCH_MOUSE = 1 or 0 still
forces either behaviour for every session.

This is the app half of the fullscreen-foreground topic, whose win32u half
gives a full-screen window shown with activation the foreground (the same
GTA V Enhanced run).

Squashed from #293.

Signed-off-by: bahacan16 <190844990+bahacan16@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@thebcd69
thebcd69 deleted the pr/foreground-rules branch October 18, 2026 11:21
iediot pushed a commit to iediot/Madeira that referenced this pull request Oct 18, 2026
…d while none is in front (willfaust#293)

iOS has no window manager, and Windows' foreground lock kept GTA V Enhanced (started by its launcher) and Horizon Zero Dawn out of the foreground, so they got no input. The full-screen rule is on by default; the main-window rule is opt-in (Horizon Zero Dawn's list sets it). The app's touch gate change rides along.

---

**win32u iOS: a full-screen window shown with activation gets the foreground**

iOS has no window manager, and the wineserver keeps Windows' foreground
lock: a process that has had neither input nor the foreground may not
take it from another process unless its parent holds it. GTA V Enhanced,
started by Launcher.exe in a Madeira Dock session (madeira-bcd build
433, log 2026-10-07 19:27), asked four times to activate its 1920x1080
window after the launcher's windows had held the foreground, and sat at
its first screen with no keyboard, mouse or pad; started on its own it
played with a pad on the same build.

A window manager gives a newly shown full-screen window the activation
it asks for, so now a visible top-level window covering the whole
virtual screen, shown without SWP_NOACTIVATE, is made foreground by its
own thread at its next message poll, unless a window of its process
already is; once per show; smaller windows (launchers, dialogs) are left
to the lock, and a hidden window never takes the foreground. On by
default; MADEIRA_FULLSCREEN_FOREGROUND=0 turns it off. [fg-show] and
[winios-tree] lines log it.

Same pull request as input-foreground (its foreground-when-none call
sits in this change's poll hook). Will rebuilds libwin32u_unix.a.

---

**win32u iOS: opt-in foreground for a main window while nothing is in front**

Horizon Zero Dawn (madeira-bcd build 471, 2026-10-09 15:01) showed its
window through style changes and SetWindowPos with SWP_NOACTIVATE only,
and reads no XInput (it uses Windows.Gaming.Input), so neither the
full-screen rule nor the XInput foreground check made it foreground:
GetForegroundWindow() stayed NULL. The wineserver queues WM_INPUT only
for the foreground process and sends keys to the foreground thread's
focus, so its language menu got none of the Enter presses or taps.

With env.MADEIRA_INPUT_FOREGROUND = 1, while no window at all is
foreground, a wine thread polling its messages or posting injected input
makes its process's main window (the largest visible top-level window of
320x200 or more) foreground, at most every 250 ms; never while some
window is foreground, so it cannot take the foreground from another
process. [fg-none] logs the first 16. Off by default; the Horizon Zero
Dawn list sets it.

docs/CONTROLLERS.md describes it, and MADEIRA_WGI_HOST_PADS: XInput pads
as Windows.Gaming.Input gamepads, which is willfaust/wine
pr/wine-wgi-host-pads of this wave (Will rebuilds
windows.gaming.input.dll with build/wine-pe/build-modules.sh).
tests/host/check-input-foreground.py checks the rule. Same pull request
as fullscreen-foreground. Will rebuilds libwin32u_unix.a.

---

**Touch: a Dock desktop keeps touches as the mouse; a game's line sets the gate**

While a touch controller layout is shown, the touch-mouse gate (willfaust#150) drops
the touches that miss the controls, so they do not move the mouse. In a
Madeira Dock session the desktop's windows are used with the pointer: with
the Xbox layout shown, every tap on GTA V Enhanced's window was dropped when
it started through the Rockstar Games Launcher, so the window never got the
click that would also have brought it to the front (fork build 433,
2026-10-07 19:27). In auto mode a desktop session now keeps touches as the
mouse. The gate also reads env.MADEIRA_TOUCH_MOUSE from the game's own lines
first, so a game's line applies (the Red Dead Redemption 2 and GTA V
Enhanced lists set 1).

On by default for desktop sessions; env.MADEIRA_TOUCH_MOUSE = 1 or 0 still
forces either behaviour for every session.

This is the app half of the fullscreen-foreground topic, whose win32u half
gives a full-screen window shown with activation the foreground (the same
GTA V Enhanced run).

Squashed from willfaust#293.

Signed-off-by: bahacan16 <190844990+bahacan16@users.noreply.github.com>
icey9527 pushed a commit to icey9527/Madeira-15.6 that referenced this pull request Oct 26, 2026
…d while none is in front (willfaust#293)

iOS has no window manager, and Windows' foreground lock kept GTA V Enhanced (started by its launcher) and Horizon Zero Dawn out of the foreground, so they got no input. The full-screen rule is on by default; the main-window rule is opt-in (Horizon Zero Dawn's list sets it). The app's touch gate change rides along.

---

**win32u iOS: a full-screen window shown with activation gets the foreground**

iOS has no window manager, and the wineserver keeps Windows' foreground
lock: a process that has had neither input nor the foreground may not
take it from another process unless its parent holds it. GTA V Enhanced,
started by Launcher.exe in a Madeira Dock session (madeira-bcd build
433, log 2026-10-07 19:27), asked four times to activate its 1920x1080
window after the launcher's windows had held the foreground, and sat at
its first screen with no keyboard, mouse or pad; started on its own it
played with a pad on the same build.

A window manager gives a newly shown full-screen window the activation
it asks for, so now a visible top-level window covering the whole
virtual screen, shown without SWP_NOACTIVATE, is made foreground by its
own thread at its next message poll, unless a window of its process
already is; once per show; smaller windows (launchers, dialogs) are left
to the lock, and a hidden window never takes the foreground. On by
default; MADEIRA_FULLSCREEN_FOREGROUND=0 turns it off. [fg-show] and
[winios-tree] lines log it.

Same pull request as input-foreground (its foreground-when-none call
sits in this change's poll hook). Will rebuilds libwin32u_unix.a.

---

**win32u iOS: opt-in foreground for a main window while nothing is in front**

Horizon Zero Dawn (madeira-bcd build 471, 2026-10-09 15:01) showed its
window through style changes and SetWindowPos with SWP_NOACTIVATE only,
and reads no XInput (it uses Windows.Gaming.Input), so neither the
full-screen rule nor the XInput foreground check made it foreground:
GetForegroundWindow() stayed NULL. The wineserver queues WM_INPUT only
for the foreground process and sends keys to the foreground thread's
focus, so its language menu got none of the Enter presses or taps.

With env.MADEIRA_INPUT_FOREGROUND = 1, while no window at all is
foreground, a wine thread polling its messages or posting injected input
makes its process's main window (the largest visible top-level window of
320x200 or more) foreground, at most every 250 ms; never while some
window is foreground, so it cannot take the foreground from another
process. [fg-none] logs the first 16. Off by default; the Horizon Zero
Dawn list sets it.

docs/CONTROLLERS.md describes it, and MADEIRA_WGI_HOST_PADS: XInput pads
as Windows.Gaming.Input gamepads, which is willfaust/wine
pr/wine-wgi-host-pads of this wave (Will rebuilds
windows.gaming.input.dll with build/wine-pe/build-modules.sh).
tests/host/check-input-foreground.py checks the rule. Same pull request
as fullscreen-foreground. Will rebuilds libwin32u_unix.a.

---

**Touch: a Dock desktop keeps touches as the mouse; a game's line sets the gate**

While a touch controller layout is shown, the touch-mouse gate (willfaust#150) drops
the touches that miss the controls, so they do not move the mouse. In a
Madeira Dock session the desktop's windows are used with the pointer: with
the Xbox layout shown, every tap on GTA V Enhanced's window was dropped when
it started through the Rockstar Games Launcher, so the window never got the
click that would also have brought it to the front (fork build 433,
2026-10-07 19:27). In auto mode a desktop session now keeps touches as the
mouse. The gate also reads env.MADEIRA_TOUCH_MOUSE from the game's own lines
first, so a game's line applies (the Red Dead Redemption 2 and GTA V
Enhanced lists set 1).

On by default for desktop sessions; env.MADEIRA_TOUCH_MOUSE = 1 or 0 still
forces either behaviour for every session.

This is the app half of the fullscreen-foreground topic, whose win32u half
gives a full-screen window shown with activation the foreground (the same
GTA V Enhanced run).

Squashed from willfaust#293.

Signed-off-by: bahacan16 <190844990+bahacan16@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
icey9527 added a commit to icey9527/Madeira-15.6 that referenced this pull request Oct 26, 2026
…me, lighter library cards

Input: a tap on a window that is not foreground went through
WM_MOUSEACTIVATE -> set_foreground_window, the foreground lock refused it
and the button-down was eaten, so only the second tap reached the game.
Retry the activation internally and deliver the click
(MADEIRA_CLICK_FOREGROUND=0 restores Wine's behaviour, [fg-click] logs it).
MADEIRA_INPUT_FOREGROUND from willfaust#293 is on by default here.

Steam: the launch-time library refresh is cut off when a game takes the
connection; after the session, refresh a stale library instead of only
the playtime.

Library: not-downloaded Steam cards drew three live blur layers each
(~170 cards); use one, flattened with drawingGroup.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants