Jumps to the arrows layer when rightalt is pressed and jumps back on release. One can also map a key to multiple ones like a: leftshift+k1 which results in !, at least for an English or GermanĪside from remapping keys, there are a bunch of other actions available, e.g. with a German layout where the yĪnd z keys are swapped in comparison to the English layout, but the name of the z key is y and vice versa. The name of a key does not necessarily match what is printed on your keyboard, e.g. Alternatively you can also use the keycode in the parentheses, which is 100 in this case. debug flag, press the key and look for an output like Pressed: rightalt (100), which tells you that the name of the If you do not know the name of a key, you can start mouseless with the
One can define an arbitrary number of layers, each with an arbitrary number of bindings, e.g. name: arrows passThrough: false bindings:Į: up s: left d: down f: right q: esc w: backspace r: delete v: enter # _ is the wildcard key, which matches any key that is not mapped _: rightalt+_ # quit mouse layer q: layer initial # keep the mouse layer active space: layer mouse r: reload-config l: move 1 0 j: move -1 0 k: move 0 1 i: move 0 -1 p: scroll up n: scroll down leftalt: speed 4.0 e: speed 0.3 capslock: speed 0.1 f: button left d: button middle s: button right # move to the top left corner k0: "exec xdotool mousemove 0 0 " # another layer for arrows and some other keys name: mouse # when true, keys that are not mapped keep their original meaning passThrough: true bindings: # when tab is held and another key pressed, activate mouse layer tab: tap-hold-next tab toggle-layer mouse 500 # when a is held for 300ms, activate mouse layer a: tap-hold a toggle-layer mouse 300 # right alt key toggles arrows layer rightalt: toggle-layer arrows # switch escape with capslock esc: capslock capslock: esc # a layer for mouse movement useful for setting the keyboard layout # startCommand: "setxkbmap de" # the default speed for mouse movement and scrolling baseMouseSpeed: 750.0 baseScrollSpeed: 20.0 # the time it takes to accelerate to baseMouseSpeed (in ms), 0 to reach top speed immediately mouseAccelerationTime: 200.0 # the shape of the acceleration curve, 1.0 is linear, higher values have more time at low speeds mouseAccelerationCurve: 2.0 # speed of the mouse when it starts moving startMouseSpeed: 0.0 # same for deceleration mouseDecelerationTime: 300.0 mouseDecelerationCurve: 3.0 # the rest of the config defines the layers with their bindings layers: # - "/dev/input/by-id/SOME_KEYBOARD_REPLACE_ME-event-kbd" # this is executed when mouseless starts, e.g. So, for basic “blind send” cross Vera/LinuxMCE compatibility should be trivial, but it’s the interactive part that gets more complex.# the keyboard devices it reads from, if no devices are specified, it reads from all devices:
What does make the Vera/LinuxMCE more difficult is that if you want to provide the user interactive, real-time feedback, so he can see for sure that his command is being processed, see a ‘busy’ indicator while it’s in process, and it turns to an ‘ok’ or ‘fail’, that makes the UI experience a lot better, but it requires vera’s zwave_status data, and there is no equivalent in LinuxMCE.
MOUSELESS ANDROID ANDROID
If your Android app uses C, you could also use the libDCECommon library.
MOUSELESS ANDROID CODE
So it’s only a couple lines of code that’s different. In that MessageSend function, it would just have an ‘if’ for Vera vs. Then everywhere in your code you just call the function to send the message without worrying about the back-end. Presumably in your code, you have a function responsible for sending the message, which could use the same declaration like LinuxMCE/Vera: MessageSend( long dwDeviceIDFrom, long dwDeviceIDTo, long dwPriority, long dwMessageType, long dwID, unsigned long dwParameterCount, … ) I don’t this should be an issue to preserve support with LinuxMCE.
0 kommentar(er)
