JNativeHook registration error support #10

New issue

Closed

opened 2015-12-08 10:52:06 -05:00 by gered · 0 comments

gered commented

2015-12-08 10:52:06 -05:00

(Migrated from github.com)

Since we currently require use of JNativeHook for global and non-global hotkeys due mainly to the differences in key codes used, we really need to get this right as right now I think it's still too easy for the user to blindly click through the prompts/messages that come up and then potentially not realize why their hotkeys don't work.

Or, I need to write a key code translation layer to allow the user to keep using the app normally even if JNativeHook events are not registered (and so they aren't using global hotkeys).

I think the handling for this is still a little bit "off." The latest version of JNativeHook that we now use is good in that it seems to have some ability to prompt some OS notifications to allow the user to allow the app (Llanfair) to get whatever permissions are necessary to hook global key events, but the user can choose to ignore this and try to continue using the app. Since we currently require use of JNativeHook for global _and_ non-global hotkeys due mainly to the differences in key codes used, we really need to get this right as right now I think it's still too easy for the user to blindly click through the prompts/messages that come up and then potentially not realize why their hotkeys don't work. Or, I need to write a key code translation layer to allow the user to keep using the app normally even if JNativeHook events are not registered (and so they aren't using global hotkeys).

This repo is archived. You cannot comment on issues.