Archive:MINIX A2: Difference between revisions
No edit summary |
mNo edit summary |
||
(11 intermediate revisions by 4 users not shown) | |||
Line 27: | Line 27: | ||
| [[File:b_up.png|70px]] || 0xf080 || up || Navigate Up || keyboard.xml || <up>Up</up>||'''Works by default''' | | [[File:b_up.png|70px]] || 0xf080 || up || Navigate Up || keyboard.xml || <up>Up</up>||'''Works by default''' | ||
|- | |- | ||
| [[File:b4.png|70px]] || || leftclick || Select || mouse.xml || <leftclick>Select</leftclick><br /><mousedragend>Select</mousedragend>|| | | [[File:b4.png|70px]] || || leftclick || Select || mouse.xml || <leftclick>Select</leftclick><br /><mousedragend>Select</mousedragend>||available starting in version 15 | ||
|- | |- | ||
| [[File:b_down.png|70px]] || 0xf081 || down || Navigate down || keyboard.xml ||<down>Down</down> ||'''Works by default''' | | [[File:b_down.png|70px]] || 0xf081 || down || Navigate down || keyboard.xml ||<down>Down</down> ||'''Works by default''' | ||
Line 35: | Line 35: | ||
| [[File:b_right.png|70px]] || 0xf083 || right || Navigate Right || keyboard.xml ||<right>Right</right> ||'''Works by default''' | | [[File:b_right.png|70px]] || 0xf083 || right || Navigate Right || keyboard.xml ||<right>Right</right> ||'''Works by default''' | ||
|- | |- | ||
| [[File:b5.png|70px]] || || rightclick || Back || mouse.xml || <rightclick>Back</rightclick><br /><mouserdragend>Back</mouserdragend>|| | | [[File:b5.png|70px]] || || rightclick || Back || mouse.xml || <rightclick>Back</rightclick><br /><mouserdragend>Back</mouserdragend>||available starting in version 15 | ||
|- | |- | ||
Line 56: | Line 56: | ||
|} | |} | ||
== mouse.xml == | == Customized MINIX NEO A2 mouse.xml == | ||
<keymap> | <keymap> | ||
Line 76: | Line 76: | ||
</keymap> | </keymap> | ||
== keyboard.xml (additions)== | == Customized MINIX NEO A2 keyboard.xml (additions)== | ||
If there are multiple keymap entries for the same key | If there are multiple keymap entries for the same key name, the last entry wins.<br/> | ||
I recommend placing manual entries at the end of the <keyboard> stanza inside <global><br /> | I recommend placing manual entries at the end of the <keyboard> stanza inside <global><br /> | ||
This saves us the effort of finding and editing | This saves us the effort of finding and editing each original key assignment | ||
.... | .... | ||
<F2>NextSubtitle</F2> | <F2>NextSubtitle</F2> | ||
Line 90: | Line 90: | ||
</keyboard> | </keyboard> | ||
</global> | </global> | ||
.... | |||
== keyboard.xml per Window customization == | |||
Another valuable tool when editing '''keyboard.xml''': there are subsections which allow you to re-assign keys while in a particular 'Window'. <br/> For example let's look this default entry: | |||
.... | |||
<FullscreenVideo> | |||
<keyboard> | |||
.... | |||
<return>OSD</return> | |||
.... | |||
</keyboard> | |||
</FullscreenVideo> | |||
.... | |||
While a video is playing (fullscreen) the <return> key will bring up the OSD, instead of executing SendClick(8) as assigned in <global><br/> | |||
If this behaviour is not desired, an additional manual entry is required in the relevant subsection.<br/><br/> | |||
== keyboard.xml per Window customization, refining remote actions == | |||
Earlier I reassigned the <return> key within the <global> section of keyboard.xml.<br/> | |||
This had one negative side effect: After manually entering text, pressing <return> would not submit the text.<br/> | |||
[[File:VirtualKeyboard_window.png|350px]] | |||
The solution is to modify the action of the <return> key while in the '''VirtualKeyboard''' Window.<br/> | |||
Add one line to the <VirtualKeyboard> section of '''keyboard.xml'''<br/> | |||
.... | |||
<VirtualKeyboard> | |||
<keyboard> | |||
.... | |||
<return>Select</return> | |||
.... | |||
</keyboard> | |||
</VirtualKeyboard> | |||
.... | |||
== remote.conf example for amlogic boxes == | |||
/etc/amremote/remote.conf | |||
Example settings needed to map the power button (note - this only applies once the device has booted, the initial power on detection appears to be in hardware) | |||
.... | |||
factory_code = 0xfe010001 | |||
key_begin | |||
0x18 116 # power | |||
key_end | |||
.... | .... |
Latest revision as of 02:44, 10 September 2020
Customized MINIX NEO A2 mouse.xml
<keymap> <global> <mouse> <leftclick>Select</leftclick> <rightclick>Back</rightclick> <middleclick>noop</middleclick> <doubleclick id="0">noop</doubleclick> <longclick id="0">noop</longclick> <wheeldown>noop</wheeldown> <wheelup>noop</wheelup> <mousedrag>noop</mousedrag> <mousemove>noop</mousemove> <mousedragend>Select</mousedragend> <mouserdragend>Back</mouserdragend> </mouse> </global> </keymap>
Customized MINIX NEO A2 keyboard.xml (additions)
If there are multiple keymap entries for the same key name, the last entry wins.
I recommend placing manual entries at the end of the <keyboard> stanza inside <global>
This saves us the effort of finding and editing each original key assignment
.... <F2>NextSubtitle</F2> <home>AudioNextLanguage</home> <return>SendClick(8)</return> <F1>Stop</F1> <prev_track>PageUp</prev_track> <next_track>PageDown</next_track> </keyboard> </global> ....
keyboard.xml per Window customization
Another valuable tool when editing keyboard.xml: there are subsections which allow you to re-assign keys while in a particular 'Window'.
For example let's look this default entry:
.... <FullscreenVideo> <keyboard> .... <return>OSD</return> .... </keyboard> </FullscreenVideo> ....
While a video is playing (fullscreen) the <return> key will bring up the OSD, instead of executing SendClick(8) as assigned in <global>
If this behaviour is not desired, an additional manual entry is required in the relevant subsection.
keyboard.xml per Window customization, refining remote actions
Earlier I reassigned the <return> key within the <global> section of keyboard.xml.
This had one negative side effect: After manually entering text, pressing <return> would not submit the text.
The solution is to modify the action of the <return> key while in the VirtualKeyboard Window.
Add one line to the <VirtualKeyboard> section of keyboard.xml
.... <VirtualKeyboard> <keyboard> .... <return>Select</return> .... </keyboard> </VirtualKeyboard> ....
remote.conf example for amlogic boxes
/etc/amremote/remote.conf
Example settings needed to map the power button (note - this only applies once the device has booted, the initial power on detection appears to be in hardware)
.... factory_code = 0xfe010001 key_begin 0x18 116 # power key_end ....