Macros with modifiers

[fire]

I would like to make a macro that does one thing when shift is pressed and another thing when shift is not pressed. Is there a way to do that?

How do I detect what modifiers are pressed when I run the macro?

[merlin (Michael Richters)]

Keyboard.wasModifierActive(Key mapped_key);

[fire]

Thanks - I’m not sure I understand how that works.

Do I use that within a macro?

Does it return true if any modifier was on? How do I determine which modifier was on? Do I use wasLeftShiftActive(), was LeftControlActive(), etc.?

[fire]

Oh ok, it’s wasModifierActive(Key_LeftShift).

These threads are also helpful:

Is there a way to change the effect of chorded modifier keys without making them layer keys?

The easiest, in my opinion, would be a custom event handler hook, something along these lines: Key customControls(Key mapped_key, byte row, byte col, uint8_t key_state) { // If none of the controls are pressed, fall through. if (!kaleidoscope::hid::wasModifierKeyActive(Key_LeftControl) && !kaleidoscope::hid::wasModifierKeyActive(Key_RightControl) { return mapped_key; // Either left or right control is active! // If the key isn't C, fall through if (mapped_key != Key_C) …

Some funky shift customizations I’d like to make

Yeah… hm. Perhaps releaseing shifts, then sending a report, then the backslash would help? And do the release+report combo only on keyToggledOn, not while keyIsPressed? Just a hunch. (Sorry for the brevity, kinda time-pressed here and can’t elaborate :/)

Mapping International Characters

What do you get when you type Fn+shift+unicode macro when using that sketch?

[merlin (Michael Richters)]

Sorry for not providing more information; I was short on time just then.

[fire]

If I use kaleidoscope::hid::wasModifierKeyActive it works fine. But with Keyboard.wasModifierActive I get the following error:

E:\User\Documents\Arduino\Model01-Firmware-Jeremy\Model01-Firmware-Jeremy.ino: In function 'const macro_t* macroAction(uint8_t, uint8_t)':

Model01-Firmware-Jeremy:683: error: no matching function for call to 'Keyboard_::wasModifierActive(Key)'

         if (Keyboard.wasModifierActive(Key_LeftShift) || Keyboard.wasModifierActive(Key_RightShift))

                                                     ^

E:\User\Documents\Arduino\Model01-Firmware-Jeremy\Model01-Firmware-Jeremy.ino:683:53: note: candidate is:

In file included from C:\Users\User\AppData\Local\Arduino15\packages\keyboardio\hardware\avr\1.22.0\libraries\KeyboardioHID\src/KeyboardioHID.h:48:0,

                 from C:\Users\User\AppData\Local\Arduino15\packages\keyboardio\hardware\avr\1.22.0\libraries\Kaleidoscope\src/key_defs.h:16,

                 from C:\Users\User\AppData\Local\Arduino15\packages\keyboardio\hardware\avr\1.22.0\libraries\Kaleidoscope\src/key_events.h:5,

                 from C:\Users\User\AppData\Local\Arduino15\packages\keyboardio\hardware\avr\1.22.0\libraries\Kaleidoscope\src/Kaleidoscope.h:24,

                 from E:\User\Documents\Arduino\Model01-Firmware-Jeremy\Model01-Firmware-Jeremy.ino:26:

C:\Users\User\AppData\Local\Arduino15\packages\keyboardio\hardware\avr\1.22.0\libraries\KeyboardioHID\src/MultiReport/Keyboard.h:60:11: note: boolean Keyboard_::wasModifierActive(uint8_t)

   boolean wasModifierActive(uint8_t k);

           ^

[craigdissel (Craig Disselkoen)]

@fire

If I use kaleidoscope::hid::wasModifierKeyActive it works fine.

I believe this is the “correct” / encouraged way to do this (it uses the Kaleidoscope HID facade). User code should “not” use HID objects like Keyboard directly. Someone else can correct me if I’m wrong.