lopondemand.blogg.se

1. #SOMETHING STEALING FOCUS WINDOWS PROCESS MONITOR INSTALL#
2. #SOMETHING STEALING FOCUS WINDOWS PROCESS MONITOR WINDOWS 10#
3. #SOMETHING STEALING FOCUS WINDOWS PROCESS MONITOR CODE#

Protected override void OnExit(ExitEventArgs e) This._focusController = new FocusController() Protected override void OnStartup(StartupEventArgs e)

Owning application should release mutex

#SOMETHING STEALING FOCUS WINDOWS PROCESS MONITOR CODE#

Private static void KillInstance(int code = 0) IsAlreadyInUse = !_instanceMutex.WaitOne(TimeSpan.Zero, true) _instanceMutex = new Mutex(true, Constants.ApplicationKey) / Checks if application is already running. Private FocusController _focusController The last piece is the implementation of the FocusController from App.xaml: If (currentProcess = null || string.IsNullOrEmpty(currentProcess.MainWindowTitle)) currentProcess must exist, and the MainWindowTitle must be valid. Var currentProcess = processes.FirstOrDefault(x => x.MainWindowHandle = _currentHandle) Var activeWindowHandle = GetForegroundWindow() This._timer.Tick += (s, e) => this.EvaluateAsync() / Initializes a new instance of the class. To do this we are going to create a controller to facilitate all our focus needs: Now that we have identified the P/Invoke piece, let’s look at how we can implement this effectively with said timer in a WPF application. Public static extern IntPtr GetForegroundWindow() Public static extern bool LockSetForegroundWindow(uint uLockCode) For this solution we will use the following methods: In my opinion, the C# community was right in thinking the best approach is to get on the P/Invoke track.įor this solution the key is LockSetForegroundWindow on a timer. For a long while, this left us SOL and drifting in space looking for the answer… that is until now. In the modern versions of Windows, this override no longer works. HKEY_CURRENT_USER\Control Panel\Desktop\Foreground\LockTimeout This involved changing the following registry key: So, back in the early 2000’s we had the Windows XP PowerToy called TweakUI which allowed us to control how initialized windows interacted with the desktop environment. So, now we need to suffer for Fred’s sins. Q: Why does Windows do this and why isn’t there a setting to fix this?Ī: Remember Fred Johnson who lived down the street in the 70’s? You know… that slightly overweight jerk that bullied the smart kids? Well, one day on the way home from school he kicked Billy Gates dog and said something off color about his “parentage”. No frills, no crap, no more of this nonsense. We are going to stop windows from stealing focus with C#.

Based on this information, I think it's fair to point out that this focus issue does NOT appear to be the fault of Display Fusion (at least directly), but hopefully you can find a hack around it.That’s what’s up.

As an aside it's a beautiful looking app but all that beauty can't make up for the fact that it's a clusterphuck of usability issues at the moment so it's not surprising to me that it's causing problems. So it's definetely something bizarrely specific to that specific app. The Xbox Beta app is built on Electron, but Electron is definetely NOT the culprit since both Slack and VSCode are built with Electron and neither of those apps are causing such issues.

#SOMETHING STEALING FOCUS WINDOWS PROCESS MONITOR INSTALL#

Below is a link to the exact app in case you aren't familiar with it (I think it requires you to be a Windows Insider to install since it's still in Beta). The moment I launch the Xbox Beta app and minimize it to the system tray, the issue resumes exactly as before.

#SOMETHING STEALING FOCUS WINDOWS PROCESS MONITOR WINDOWS 10#

Hi Keith, I've re-enabled the DisplayFusion taskbar (instead of the Windows 10 one) and can confirm that the issue goes away completely if I do NOT have the Xbox Beta app running in the system tray.