hasu@tmk

Great. Thanks. 006F and 0070 is marked as "reserved" in HID usage table spec, probably Apple specific usages.

Display Brightness Controls: http://www.usb.org/developers/hidpage/HUTRR41.pdf I confirmed 0x6F and 0x70 works also on Windows 10. ``` ACTION_USAGE_CONSUMER(0x6F) ACTION_USAGE_CONSUMER(0x70) ```

And just confirmed Brightness Increment and Decrement(0x6f and 0x70) work with Ubuntu16.04 on Thinkpad x201s too.

`AL Email Reader(18A)` is recognized as 'Photo viewer' on Windows10 weirdly. https://geekhack.org/index.php?topic=88720.msg2439662#msg2439662

**EDIT: posted this here accidentally. Ignore this.**

Reopen this.

Added support for Display Brightness Control at 15434c3a167f0c992e0f55af5d1d6d2ea6a31878 https://github.com/tmk/tmk_keyboard/blob/15434c3a167f0c992e0f55af5d1d6d2ea6a31878/tmk_core/common/actionmap.h#L422-L423 https://github.com/tmk/tmk_keyboard/blob/15434c3a167f0c992e0f55af5d1d6d2ea6a31878/tmk_core/common/keycode.h#L177-L178

``` Tapping events of Dual role key =============================== 2014/04/24 Dual role variations -------------------- From user's point of view there can be two variations. 1. key/mod mainly used as a key...

Current implementation of `ACTION_MODS_TAP_KEY` works like 'modifier key' rather than 'alpha key'. (See #215) Probably it works well when it is placed on 'modifier key' but not when on 'alpha...

For refernece, QMK has build option IGNORE_MOD_TAP_INTERRUPT to change ACTION_MODS_TAP_KEY behaviour as discussed in #215. https://github.com/qmk/qmk_firmware/blob/732a115b32a9c6aa529c53ef52a9689b5901411d/tmk_core/common/action.c