Gopher stops when task manager is open

[mattwright324]

Using Windows 10, when starting task manager from the task bar, Gopher stops working. When task manager is minimized with the mouse, Gopher starts works again. It only seems to stop working when task manager is visible.

[Tylemagne]

Does it do the same thing if you run it as an administrator? I know admin mode is required for it to function when the OSK is open, so maybe it's the same with task manager.

[mattwright324]

Administrator does solve the issue! Some behavior I noted though:

• Admin Gopher (AG) has no issue with task manager (TM).
• Normal Gopher (NG) works okay when TM started and visible before it. Cannot interact with TM though.
• NG stops working while TM started and visible after NG was started.
• At least in Windows 10, the new On-Screen-Keyboard or "Touch Keyboard" has no issues with NG. Was this a problem with the old OSK?

[kkaja123]

Task Manager does require elevated access. Therefore, this is working as expected, and there is nothing to fix regarding the Task Manager.

When I tried the Windows 10 OSK without running Gopher as admin, Gopher was still enabled but could not interact with the OSK. So that's strange...

[mattwright324]

Apparently the "On Screen Keyboard" and "Touch Keyboard" in Windows 10 are different, separate programs so that might be reason. They do look very similar though; main difference seems to be OSK is in a movable window and the TK is unmovable at the bottom of the Screen. I don't have a controller to test with right now but the Touch Keyboard works fine; I have not tested with the OSK.

[kkaja123]

Okay, I see now. The "On-Screen Keyboard" does require admin rights and the "Touch Keyboard" does not. It's weird that they have two different versions of the OSK, but it's good to know that the Touch Keyboard will work with Gopher in non-elevated access mode.