Skip to content

Separate game responses from native window events - #121

Open
Krisztiaan wants to merge 1 commit into
OpenTS-Developers:mainfrom
Krisztiaan:refactor/window-event-boundary
Open

Separate game responses from native window events#121
Krisztiaan wants to merge 1 commit into
OpenTS-Developers:mainfrom
Krisztiaan:refactor/window-event-boundary

Conversation

@Krisztiaan

@Krisztiaan Krisztiaan commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Move paint, right-button release, and mouse-wheel game responses out of the Win32 procedure.
  • Keep native message decoding and window validation in the Win32 shell.
  • Name the video refresh-rate update for the state it sets, not its native event source.
  • Preserve externally visible behavior and compatibility boundaries.

Validation

  • uv run --no-project --python 3.13.7 --with-requirements manual/tools/requirements.txt python manual/tools/manage.py update
  • uv run --no-project --python 3.13.7 --with-requirements manual/tools/requirements.txt python manual/tools/manage.py check
  • Win32 Debug, Win32 Release, and runtime were not run locally; CI covers the supported builds.

Documentation

Added a 0.2.0 internal change record.

@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown

Development builds of 2126839:

The links work without a GitHub account. Artifacts expire after 90 days, and this comment follows the latest successful build.

@Krisztiaan
Krisztiaan force-pushed the refactor/window-event-boundary branch from a6064a8 to 2126839 Compare September 3, 2026 20:35
@Krisztiaan Krisztiaan changed the title Separate game window responses from Win32 events Separate game responses from native window events Sep 3, 2026
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.

1 participant