Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Show in explorer stays in background
See original GitHub issueDescription
Upon pressing ctrl+shift+f or “show in explorer” from the menu or the context menu of changed files, file explorer opens properly but its window stays in the background. It would help workflow if focus goes to this window upon activation.
Version
GitHub Desktop version: 0.6.2
OS version: Microsoft Windows [Version 10.0.15063]
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Window opens in background. - Microsoft Community
I have a shortcut in start that opens a File Explorer folder. If that folder is being displayed in the background and I...
Read more >File Explorer window stuck in the background
Hello. I have 4 file explorer windows open, plus a couple of apps like Chrome, Outlook, LibreOffice. I click on 1 of file...
Read more >How to Stop Explorer.exe From Running in the Background
1. Click the Windows "Start" button. · 2. Press and hold the "Ctrl" and "Shift" keys. Right-click on any empty spot on the...
Read more >"Show Desktop" sometimes sets a window to "always on top"
Open Task Manager (You can use the shortcut Crtl + Shift + Esc ). Click on the Processes Tab and locate the process...
Read more >"Show in explorer.." opens window in background [Archive]
One solution (from url above and others) seems to be to open REGEDIT, go to key > HKEY_CURRENT_USER\Control Panel\Desktop, and set ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Ah, yeah, here it is: https://github.com/electron/electron/issues/4349. Sounds like a known issue but a simple enough fix.
I vaguely recall seeing an issue where this would happen if the function was called from the renderer. The fix was to call it from the main process instead.