Honor the extendedExecutionSession flag in windows.gaming.input.gamepad.vibration
UWP desktop app targeting Windows 17763, requesting and being granted an extendedExecutionSession can target the vibration motors through a windows.gaming.input.gamepad's Vibration interface but once the app gets minimized applying the Vibration property silently fails.
Please honor the extendedExecutionSession context, thanks.
Tim Demulder commented
Hi Clint, sorry for the delay in responding to you: turns out I'm not getting notified of any replies here.
The use case is as follows: our application gets minimized because another application gets the focus (browser/e-mail/IM/...) and the minimized application wants to get the user's attention to switch back to it by vibrating the controller's motors as a heads-up.
If the application is minimized, can you explain the scenario where a gamepad's vibration would still be needed? If minimized, another application could have context for the pad.