fbpx
  Wednesday, 17 April 2019
  1 Replies
  3.2K Visits
  Subscribe
Because the number of keys on the KeyMouse Alpha is understandably limited, and with two of those keys on the white layer being taken by FN Blue and FN Yellow, there is really little space for an extra fn key on the white layer. This got me thinking:

There are quite a few keys like the Tab, that don't really get much use as Hold-and-repeat keys; you typically tap them once or twice to get the desired result, but almost never have the need to hold them for the auto-repeat functionality to kick in.

Instead of issuing a TAB Down signal upon keydown, the KeyMouse could delay until the key is released and issue it as an immediate keypress (Tab up, Tab down), While being held, however, it could very well function as a layer shift key, say, Fn Red. The pseudo-code would go like this:

On KeyDown
immediateIntent = true
enter fn layer

While Down,
On KeyDown (for anoter key)
immediateIntent = false
Do whatever the other key needs to do

On KeyUp
if immediateIntent == true
issue original keydown
issue original keyup
else
exit fn layer

I assume this would need to be implemented in the logic board, as well as interfaced by the application. Would it be possible though?
3 years ago
·
#1646
These are good ideas. We will add this to our feature request list. Some users have asked for similar things with the FN layers (if tap and release FN Key, just go into the layer for the next single key, but if held down stay in the layer until released).
  • Page :
  • 1
There are no replies made for this post yet.
Be one of the first to reply to this post!
Submit Your Response
Upload files or images for this discussion by clicking on the upload button below.
Supported: gif,jpg,png,jpeg,zip,rar,pdf
· Insert · Remove
  Upload Files (Maximum 2MB)
Captcha
To protect the site from bots and unauthorized scripts, we require that you enter the captcha codes below before posting your question.