plex-media-player
plex-media-player copied to clipboard
PMP never has focus after re-launching after PMP update is installed
Test environment
PMS Version: 1.14.0.5470 PMP Version: 2.24.0.924 and all versions before it for last year since i started using PMP Platform (Windows/OSX/Embedded): Windows 10 x64
This happens on all 3 of my HTPCS running Windows. I only use these machines via MCE remote - no mouse or keyboard.
PMP is lauched on windows startup PlexMediaPlayer.exe --tv --fullscreen on all 3
Steps to reproduce
- Get prompted to install a new PMP update within PMP, click YES
Current behavior
- The PMP installer updates PMP to the latest Version, then relaunches PMP application automatically the re-laucnhed application after update, does not have focus - IT IS fullscreen on the monitor/tv, but not in focus. this is extremely annoying when you are using a remote, no mouse and KB to alt tab focus back
Expected behavior
- PMP should update, and re-launch with the application been in FOCUS, the same way it was originally launched before the update, without needed to alt tab on the keyboard to get focus back
Plex Media Player Installer.log Plex Media Player Installer_000_pmp.log PlexMediaPlayerAFTERUPDATE-NOFOCUS.log PlexMediaPlayerBEFOREUPDATE.log
Hi @dan-the-man-nz 👋
the re-laucnhed application after update, does not have focus - it if fullscreen on the monitor/tv, but not in focus
Extremely annoying for sure. I wonder if there's a helper application restarting PMP that is dropping the ball on focusing the window post launch. I could see it being annoying in some cases to steal focus after the update is applied but I definitely thing fullscreen w/o focus is a greater annoyance.
I'll put this in triage for the TV team project. I think ultimately it's going to require someone to look into how the the application gains focus from the C++ side.
thanks for that!
Hi
was this fixed? i have not noticed this issue for the last month or so of updates?
Super strange. No, we haven't made a change address this. Will close until we see it again (sounds like a slipper race condition issue).
please reopen the same issue happened on 2 different machines on the last update