Following on from #124 and #161, we're waiting for 1.1.2 of WinAppSDK or beyond to make progress on this front due to blocking issues with CI and MSTest Discovery. (Also see MicrosoftDocs/windows-dev-docs#3887)
Once those are resolved in the WinAppSDK we can resume investigating our InputInjection approach which appears to work (at least for mouse click) without issue on UWP.
From original thread comment:
Thanks @Sergio0694, yeah I was roughly thinking something like:
await SimulateInput.StartTouch()
.MouseDown(coord)
.MouseMove(cx, cy, seconds: 0.5, points: 10)
.MouseUp()
.Execute();
As we need to preface and end the operation with initializing/uninitializing the touch injector code, as well as generate/use a unique pointer id across the instructions (and if we want to use relative positioning between operations keep track of the initial point).
Anyway, bit more investigation to do, as not sure if this is going to run in the CI yet (though even then may have value).
Originally posted by @michael-hawker in #124 (comment)
Current work in llama/input-injection-test branch. Now in llama/input-injection-2025 in tooling and main repos.
Following on from #124 and #161, we're waiting for 1.1.2 of WinAppSDK or beyond to make progress on this front due to blocking issues with CI and MSTest Discovery. (Also see MicrosoftDocs/windows-dev-docs#3887)
Once those are resolved in the WinAppSDK we can resume investigating our InputInjection approach which appears to work (at least for mouse click) without issue on UWP.
GridSplitteras a test case and see if we can:From original thread comment:
Originally posted by @michael-hawker in #124 (comment)
Current work inNow inllama/input-injection-testbranch.llama/input-injection-2025in tooling and main repos.