2018-04-21, 01:04
Simple issue really, when I create a new process using execwait, the keyboard is not available to the resulting process because KODI still has the input locked. When the process closes, all the keystrokes that should have been sent to the process that spawned from execwait are sent to KODI all at the same time.
This old feature request would have resolved the issue and allow execution of processes while allowing them to use all available inputs without conflicts. Was it ever included?
https://trac.kodi.tv/ticket/6122#no1
Maybe there is a better way to call a sub-process from KODI while freezing KODI so it can't do anything or use any CPU and releasing the inputs to the resulting processes?
Maybe there's a python command I can issue to de-init the inputs and then re-init when the process closes?
This old feature request would have resolved the issue and allow execution of processes while allowing them to use all available inputs without conflicts. Was it ever included?
https://trac.kodi.tv/ticket/6122#no1
Maybe there is a better way to call a sub-process from KODI while freezing KODI so it can't do anything or use any CPU and releasing the inputs to the resulting processes?
Maybe there's a python command I can issue to de-init the inputs and then re-init when the process closes?