I’ve just upgraded my UHK60 from R11 to R16 (in steps, not in one hit lol), and pretty much everything is working OK!!
One issue I’ve got is my Left Ctrl macro. I do have a workaround but would like to see if it can be fixed.
The macro (which worked perfectly on R11) is:
holdKey leftShift
ifDoubleTap tapKey capsLock
This was assigned to Left Shift key, and aside from instances where I typed “Hi John” where the H and J were tapped inside the time window (resulting in “Hi JOHN”), it was great.
Now there’s a short delay on the Shift kicking in, so when I go to capitalise a word, most of the time it doesn’t fire and I have to go back and hold the Shift key a fraction longer for it to kick in.
Having said that, I’ll probably move the Caps Lock to an unused key, as I rarely if ever use it, but wanted to post this here in case there’s a better way to do this function. I have played with the timers, and I think dropping the Timeout to 200ms helped a bit, but I don’t have any empirical evidence of this.
Both ways work fine with no noticeable delay here on UHK80 (as long as you fix the uppercase T typo in ifDoubleTap).
BUT, while checking this, I noticed that Agent didn’t give me an error notification for the ifDoubleTap typo when saving to keyboard without first mapping it to a key. After mapping the macro to a key, and then saving to keyboard, it throws the error…
I’m using latest master branch FW v16.1.1 #c90ed9e, and latest master Agent v9.0.1 8c78f8c. I see there’s been a lot going on lately, so I’m not sure when it started (or if it’s just me).
This was assigned to Left Shift key, and aside from instances where I typed “Hi John” where the H and J were tapped inside the time window (resulting in “Hi JOHN”), it was great.
This is interesting. Are you saying that your flow was:
tap shift+h
write 'i ’
tap shift+j, this activates the doubletap caps lock
you write OHN using the caps lock rather than shift
If so, we may have simply fixed doubletap to get broken by an intermediate action.
BUT, while checking this, I noticed that Agent didn’t give me an error notification for the ifDoubleTap typo when saving to keyboard without first mapping it to a key. After mapping the macro to a key, and then saving to keyboard, it throws the error…
Macro args. Macros with args need to be validated in context of their arguments, so at the moment we only validate macro bindings.
I see this is nonintuitive and problematic and will come up with a fix soon.
Thanks everyone for the input, and the ifDoubleTap typo was mine in this post - the macro is correct.
I’ve swapped the order, and while the “Hi JOHN” behaviour is still happening, it may have fixed the delay issue. I’ll test further during the day and advise.
EDIT: Confirming behaviour is still happening. Maybe just needed the coffee to kick in so I type faster
).