Notice: This forum has been recovered from an old backup, so some content, links, and dates may be outdated. The forum is currently read-only while we restore sign-in and registration functionality. Details
If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.
If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.
[SOLVED] Launched programs appearing behind other windows
[SOLVED] Launched programs appearing behind other windows
I've noticed that, after a seemingly random period of time, any program I launch via an EventGhost shortcut situates itself behind all my other windows and flashes its taskbar entry rather than becoming the topmost window. I tried jamming a BringHwndToFront() in the System.Execute code, but this often brings the wrong window to the front, seemingly because the hWnd returned in processInformation is often incorrect. Restarting EventGhost temporarily corrects the problem, but doing this every few hours is, to say the least, annoying. Any thoughts on how we can resolve (or even troubleshoot) this?
Last edited by blackwind on Sun May 12, 2013 9:08 pm, edited 2 times in total.
/bw
Re: [SOLVED] Launched programs appearing behind other window
Finally found the perfect solution.
- Attachments
-
- patch.zip
- (3.29 KiB) Downloaded 197 times
/bw
Re: [SOLVED] Launched programs appearing behind other window
...and wouldn't you know it, my solution works without issue for over two months, and as soon as I post it, that's when it fails.
Patch updated. I've figured out how to reproduce the issue, so I'm confident this will be the final patch.
Patch updated. I've figured out how to reproduce the issue, so I'm confident this will be the final patch.
/bw