-
Notifications
You must be signed in to change notification settings - Fork 33
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
grave not working on custom remote #18
Comments
So I apparently looked in the wrong section for the keys. Windows does not have a grave. How can I set a button up to use a tilde, also how can I set a button up to use the backtick? |
Wow, I had always called it a backtick. TIL. I have a windows keyboard though, and it's on there? Sorry for the shot in the dark, but does this not do it? |
|
for the "tilde" or "backtick", (which.is "grave accent") instead of using Instead, use the function The kb.character uses the "character.keyboard" library found in unified remote, which uses UTF-8 hex coding (refer to the link at the bottom for details), but the coding is 0x60 So instead of our output will be Full string would look like the following: actions.command1 = function () Link Ref: |
I am making a custom remote that requires the grave key (the other character on the tilde key).
I set it to grave as found on the available keys list, but it does not work.
Here is my remote.lua code:
`local kb = libs.keyboard;
-- Documentation
-- http://www.unifiedremote.com/api
-- Keyboard Library
-- http://www.unifiedremote.com/api/libs/keyboard
--@help Full Screen
actions.fullScreen = function ()
kb.stroke("f");
end
--@help Pause
actions.pause = function ()
kb.stroke("space");
end
--@help Switch Screens
actions.switchSCreens = function ()
kb.stroke("grave");
end`
The text was updated successfully, but these errors were encountered: