Luke 36998 Posted March 20, 2019 Share Posted March 20, 2019 Thanks for the info. Link to comment Share on other sites More sharing options...
raymondjpg 9 Posted March 20, 2019 Share Posted March 20, 2019 (edited) Whatever the cause there are enough people affected that it is worthy of further investigation. Perhaps with a fresh install of Windows 10. This appears to have resolved the issue for me: Change the value in HKEY_CURRENT_USER\Control Panel\Desktop\ForegroundLockTimeout from 30d40 (hexadecimel) to 10 (decimel). There are a number of references on the web suggesting change the value to 0 (hexadecimel) but that did not work for me. I checked with an installation of Theater in one of my Windows 7 pcs that did not have this issue of loss of focus, and the registry value there is 30d40 (hexadecimel). It appears that Theater was unable to cope with my fresh install of Windows 10 where the registry value looks by default to be 30d40 (hexadecimel). When I have some time I will check with my other Windows 10 HTPCs to see if the registry value is anything other than 30d40 (hexadecimel). I doubt it as I have never had occasion to modify this value before. As it was necessary to modify the value on my fresh install of Windows 10, there could well be some issue other than ForegroundLockTimeout at play. I hope that other applications do not fall foul of my registry tweak, but so far I haven't seen any evidence of that. I don't know if the registry fix would work without replacing shell.js first. That could be checked with a fresh installation of Theater. Edited March 20, 2019 by raymondjpg Link to comment Share on other sites More sharing options...
Luke 36998 Posted March 21, 2019 Share Posted March 21, 2019 Can you try with this latest test version: https://www.dropbox.com/s/zj75bqjajgjerey/theater.zip?dl=0 It simplifies window management in the app which more than likely will help with this. Thanks. Link to comment Share on other sites More sharing options...
raymondjpg 9 Posted March 21, 2019 Share Posted March 21, 2019 Can you try with this latest test version: https://www.dropbox.com/s/zj75bqjajgjerey/theater.zip?dl=0 It simplifies window management in the app which more than likely will help with this. Thanks. Yes. This standalone version appears to retain focus even when the (apparent default) value of 30d40 (hexadecimel) is set for HKEY_CURRENT_USER\Control Panel\Desktop\ForegroundLockTimeout. As I am more in favour of applications being modified to cope with the idiosyncracies of operating systems than vice versa I'll stick with this version until a production version that can cope with the loss of focus becomes available. Link to comment Share on other sites More sharing options...
Luke 36998 Posted March 21, 2019 Share Posted March 21, 2019 Thanks for the feedback. Link to comment Share on other sites More sharing options...
Mael 5 Posted March 21, 2019 Share Posted March 21, 2019 @@Luke Can you please let us know when this fix will make it into the official release stream? Link to comment Share on other sites More sharing options...
Luke 36998 Posted March 21, 2019 Share Posted March 21, 2019 Yes, please stay tuned to the blog for the release announcement. Thanks. 1 Link to comment Share on other sites More sharing options...
raymondjpg 9 Posted March 25, 2019 Share Posted March 25, 2019 It appears that Theater was unable to cope with my fresh install of Windows 10 where the registry value looks by default to be 30d40 (hexadecimel). When I have some time I will check with my other Windows 10 HTPCs to see if the registry value is anything other than 30d40 (hexadecimel). I doubt it as I have never had occasion to modify this value before. I encountered the loss of focus on another HTPC running Windows 10 1809, this time upgraded recently from Windows 7. Previously it appeared to be working perfectly well, but there have been some recent quality and/or security updates that look to have triggered the issue. Both HTPCs are running with the same graphics driver. A third HTPC, also running Windows 10 1809 fully patched but with a different graphics driver does not appear to have the same issue. The loss of focus turned out not to be confined to Emby Theater. It was also apparent in the external players that I use. These external players are controlled with an IR remote device that emulates keyboard strokes. The loss of focus with the external players could be overcome by running madVR in Full Screen Exclusive mode. So it appears that the issue in my case may be due to some recent Windows 10 updates, and limited to my HTPCs with a particular GFX graphics driver. Intel hasn't provided any more recent versions of GFX drivers for these HTPCs, but is instead promoting DCH drivers which look to be difficult to go back on once installed. They may resolve the issue of loss of focus, but for the time being I have stayed with the apparently problematic GFX driver and implemented the workaround of changing the value in HKEY_CURRENT_USER\Control Panel\Desktop\ForegroundLockTimeout from 30d40 (hexadecimel) to 10 (decimel). This allows both use of the current production version of Emby Theater and trouble-free use of an IR remote with the external players. Link to comment Share on other sites More sharing options...
Mael 5 Posted May 4, 2019 Share Posted May 4, 2019 Can someone confirm if this was fixed in the latest client? Link to comment Share on other sites More sharing options...
Luke 36998 Posted May 4, 2019 Share Posted May 4, 2019 I was never able to reproduce this, but given the simplified window management in the latest release, as well as the positive feedback from testers, I would think there's a very good chance you'll see better results with it. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now