version 0.6.1 is not working correctly on Win 10 about alwaysontop HOT 15 OPEN

I have the same issue (haven't tried 0.5.1 though) where keyboard stops responding in other windows.

from alwaysontop.

from alwaysontop.

I am seeing the same issue with v0.6.1 on Windows 10. The keyboard completely stops working.

Additionally, it seems to have changed my mouse cursor (!?) to a tiny one (I'm on a 4k HiDPI screen).

v0.5.1 seems to work fine.

from alwaysontop.

OK, I have a dev environment set back up, I am installing virtual machines to test the builds now (as I said before, I don't think the GKH class was changed, so obviously something between 0.5.1 and 0.6.1 is the cause) I will hopefully have an answer for you guys before too much longer.

from alwaysontop.

Just to add to the fire. Same issue here. Seems to be centric around modifier keys most of the time. Some keys just stop working others don't

from alwaysontop.

this happens to me too.

from alwaysontop.

Any news on this ?

from alwaysontop.

+1. Windows 10. I'm busy with the 4th this weekend, but based on jparnell's comment above, I'll run a diff between 0.5.1 and 0.6.1 next week and see if I can figure out the issue.

Temporary workaround is:

• Run AlwaysOnTop
• Set a window as usual
• Close AlwaysOnTop
  This releases the keyboard and keeps the selected window on top. There will be a residual context menu on the screen, but AlwaysOnTop closes the first time you hit "Exit". There's no need to hit it again.

from alwaysontop.

The problem is in AlwaysOnTop.cs, line 170 thru 173. The hook is being created with no keys set if there are no declared hotkeys. That's causing the hook listener to swallow every keystroke. Commenting those lines out doesn't seem to affect anything, though I haven't run hotkeys.

There are two possible workarounds

1. if you guys have VS, use nuget to install octokit, comment out those lines, build and publish to install the latest version. Again, I'm not sure if this will break setting new hotkeys. I don't use them and it hasn't been tested (yet)

2. in your current version, go to Settings -> Use Hotkey. Set it to true. Don't bother trying to set a hotkey yet; the app is still swallowing inputs. When AlwaysOnTop restarts, an error will be thrown because it expects a hotkey to be set. Don't worry about it--it's not a hard crash. The app will now work as intended.

@jparnell8839 if you want to give me contributor permissions I'll test this fix more thoroughly and create a pull request.

from alwaysontop.

This was driving me nuts on my day off yesterday so I took an hour this morning to really dig into it. The actual problem is in the globalKeyboardHook.cs class. Not sure who contributed this, but it's broken.

Long story short, hookProc was getting garbage collected and an error was being swallowed. Make hookProc into a class delegate that gets instantiated in the constructor and everything works as expected.

I've fixed this, cleaned up some of the code, and corrected a problem where an error was thrown if Use Hotkeys was checked but no hotkey was set. It could use quite a bit more cleanup but I'm not gonna bother if I can't commit the changes.

@jparnell8839, again, dude...you wanna hook me up with push? Otherwise I'm going to assume this repo is dead and start up a new one.

from alwaysontop.

great @wnipper +1

Can you make a PR or a fork ?

from alwaysontop.

I was googling how to revive a dead repo (not new to git, but this is the first time I've collaborated on a public project) and found out about forking. I forked and I'll update it over the course of the week. I've also got some ideas for new features I'd like to work on, like an easier way to turn AoT off for specific windows.

from alwaysontop.

I think the best is if you submit a PR to this repo with your changes, then anyone can use that PR or fork it as well thx

from alwaysontop.

@kofifus I'll submit a PR from my fork when I'm done with bug fixes.

I'm gonna go ahead and check in the changes I've made so far to my fork. It's no longer fundamentally broken, but there are still quite a few fixes that need to be made (hotkeys, for example, don't work at all).

from alwaysontop.

can confirm issue is still there on windows 10 1903 as of Jan 2020

from alwaysontop.