* Run IntegrationTests.Win32 on CI
* Skip keyboard layout tests when the layout is missing outside of CI
Tests that need a keyboard layout use KeyboardLayoutFact. On a developer
machine without the layout, they are skipped, so that tests don't change the
user's layouts. The Win32 integration test target sets AVALONIA_CI_RUN=1, and
then the tests run and load the layout.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Don't end a pending dead key to build a keyboard layout table
A table built while a dead key is pending would combine every entry with it,
and ending the dead key loses the key that the user just pressed. On Windows
10 1607 and later, the build now waits for a later call while a dead key is
pending. A layout that becomes active after startup gets its table on
WM_INPUTLANGCHANGE, before the first key in that layout.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Set AVALONIA_CI_RUN in the GitHub workflow and switch layouts through TSF in tests
The Nuke build also runs on developer machines, so the Windows workflow job
sets AVALONIA_CI_RUN instead of Build.cs.
The keyboard tests switch the process to the German layout after the window
is activated. They activate the TSF input profile, so that an active IME
doesn't keep processing the keys, and then the thread's keyboard layout.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Julien Lebosquain <julien@lebosquain.net>
Co-authored-by: Max Katz <maxkatz6@outlook.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>