https://bugs.documentfoundation.org/show_bug.cgi?id=120326
Mike Kaganski <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |difficultyMedium, easyHack, | |skillCpp --- Comment #5 from Mike Kaganski <[email protected]> --- Code pointers: The place where we should insert calls to inform OS about user input is Receiver::executeCommand in sd/source/ui/remotecontrol/Receiver.cxx Additionally/alternatively, we might consider setting an OS flag on remote connection/initiated slideshow start, and clear it on disconnection/slideshow end. This needs to be done at Communicator ctor and dtor in sd/source/ui/remotecontrol/Communicator.cxx The code to inform OS is necessarily OS/WM-specific. For Windows, informing OS about user input (in Receiver) should be done using SendInput [1], as discussed at [2]. Using PowerSetRequest [3] and/or SetThreadExecutionState [4] may be used in the Communicator, as these calls do not represent some events, but rather some state. [1] https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-sendinput [2] http://stackoverflow.com/a/1675793/1889329 [3] https://docs.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-powersetrequest [4] https://docs.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-setthreadexecutionstate -- You are receiving this mail because: You are the assignee for the bug.
