Skip to content

1.1.0-rc.2 — Hidden Editor cursor isolation

Pre-release
Pre-release

Choose a tag to compare

@VoVanRusLvSC2 VoVanRusLvSC2 released this 28 Oct 12:31

Hidden Editor cursor isolation fix for 1.1.0-rc.1. API contract 1, native protocol 16 and the existing 31 MCP tool names are unchanged.

  • Wrapped D3D9 and D3D9Ex devices discard cursor positioning, cursor bitmap and show/hide commands. The invisible render thread no longer forwards them to the driver on the input desktop.
  • The startup DLL refuses initialization outside the selected original Editor on its private desktop before installing patches or creating the rendering thread.
  • No game process is attached to or modified. GUI hooks remain scoped to owned Editor threads, with no physical input injection or desktop switching.

Validation: 122 Python tests, eight native test executables, real-DLL rejection in an unrelated test process, and hidden original-Editor startup plus two nonblack Terrain captures on a private map. The source map remained unchanged; observation recorded zero visible owned windows, foreground samples or input-desktop changes. Read-only inspection found no toolkit DLL in the same running SC2 game before and after the test. Gameplay input itself was not driven or recorded. The test worker closed.

The frozen HTTP and windowed MCP package checks passed (31 tools), and the packaged source/native hashes match the committed build. The rc.1 field/resource and camera acceptance baseline remains documented separately; a full Data audit was not repeated for this cursor fix. This is a prerelease; stable 1.0.0 remains available.

Replace the complete package and restart its owned worker to apply the change. Already running workers keep their existing DLLs. Do not hot-replace loaded DLLs or stop another session's Editor. See docs/INPUT_ISOLATION.md for details.