Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Seems not to work on Win 8.1 #1

Closed
ARF1 opened this issue Apr 12, 2016 · 9 comments
Closed

Seems not to work on Win 8.1 #1

ARF1 opened this issue Apr 12, 2016 · 9 comments

Comments

@ARF1
Copy link

ARF1 commented Apr 12, 2016

I just installed this on Windows 8.1 and while it correctly identifies when the keyboard was connected/disconnected, the function key shift does not seem to work:

When I press e.g. F10, my windows volume is muted instead. Is there any trick to running this successfully on Windows 8.1? Do you maybe have feedback from users?

Does it maybe need to be run with administrative privileges?

@jesperhh
Copy link
Owner

I am currently using it on Windows 10, and have also used it on Windows 8.1 where it worked.

The only issue I have seen is that sometimes it will stop working if the keyboard goes into power saving mode and comes back online.

Could you try making sure that the keyboard is connected and not in power saving mode and then starting the application? If that works then I can work on the issue where the keyboard comes back from power saving.

@ARF1
Copy link
Author

ARF1 commented Apr 13, 2016

@jesperhh You are completely right. After closing the app and reopening it works!

It would be great if you could get the power saving mode issue to work. I would completely understand however if this program already does all you need it to and you do not want to invest extra time fixing this. - It is very useful piece of software anyway! Thank you so much for sharing this.

Just out of curiosity:

  • Does the "keyboard / eject" button have any use on Windows? If not, I would love to have it assigned the "Del" function. "Fn + Backspace" is a bit awkward for that.
  • Would it be possible to repurpose the "apple / cmd" button on the right of the space bar as a "windows context menu" key? I do not really need two "windows start menu" keys but a "context menu" key might be useful.

@jesperhh
Copy link
Owner

Well, it annoys me as well, but I just never got around to fixing it, but now that two people are annoyed by it I should do something about it :-)

The keyboard / eject button should be remapped to sending F13 key-presses by my software (see ejectkey.cpp), but you can use SharpKeys (or another key-remapping utility) to remap that to the delete key.

The right Apple key can perhaps be remapped by itself - I don't have the keyboard right here, but you can try out SharpKeys and see if it detects the two keys as separate keys. However, if the keyboard firmware sends out the same key presses for both keys, it can't be solved in software unfortunately.

@ARF1
Copy link
Author

ARF1 commented Apr 14, 2016

@jesperhh Remapping the right windows key to the context menu key works perfectly with SharpKeys.

However, when I try to remap the "keyboard/eject" key by pressing "type key" in SharpKeys, it does not recognize that I typed the key. From what you said, it should detect that I pressed F13 right?

If I do however select F13 manually in SharpKeys and assign it to "Del" everything works as expected.

Maybe there is some minor bug with events that SharpKeys checks for when using the "type key" function but that is not being sent?

Anyways: all my key-reassignment wishes are resolved. Many thanks for your help!

@jesperhh
Copy link
Owner

@ARF1 I have released a new version that should fix the issue. It seems Windows detects the keyboard before it is actually ready to receive commands, so the initial command always fails. I have added a retry that should fix the issue. Could you verify whether this fixes your issue?

@ARF1
Copy link
Author

ARF1 commented Apr 19, 2016

@jesperhh Great! I have it installed now and will report back after observing it for a few days.

@jesperhh
Copy link
Owner

Assuming it worked :-)

@ARF1
Copy link
Author

ARF1 commented Jun 16, 2017

My apologies: I forgot this issue was still open. Everything discussed here was indeed fixed.

One issue I still have is that (very rarely) WinK760 exits/crashes without any notice. I have been unable to identify when this happens. - But no harm, no foul: it is easy enough to restart when the keymapping is no longer working...

Again many thanks for providing WinK760 for "everybody". ;-)

@jesperhh
Copy link
Owner

That's okay, good that it is fixed :-)

I will create a new issue for that, when time permits I can go over the code for potential bugs. I don't use the program much anymore myself, so I haven't encountered the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants