I’ve been using the Model01 for a couple months now, and the biggest pain that I have is alt+tab being on two different halves. I was hoping to create a macro or find a plugin that would make it easy to remap the alt+tab functionality to just one key, or map to a function key so that it can be pres…

This information is surprisingly hard to find for something which is very basic and important functionality, so it’s no surprise that you haven’t come across it. Here’s a previous thread about this, but basically of you put LALT(Key_Tab) (Or RALT(Key_Tab), really doesn’t matter) into your keymap whe…

I decided to modify this page to include that information. As I mentioned in the edit notes, not sure what I said is 100% correct nor whether it’s the right or only place to put this information, but I figured having something down somewhere was a good idea and that someone more experienced could cl…

LAlt and RALT both send the key up event, this is not what was aked for. Usually, the Tab+Alt keys initiate a pop up window, allowing you to switch between open applications/windows without using your mouse. You hold Alt and cycle through the windows by tapping the tab key. LALT(Key_Tab) sends the…

Ah I get it now. The problem with having it on just one key would be having a way for windows to know which window to end up on. You could easily do a macro omitting the alt-up of the alt-tab sequence to be able to cycle through windows with each keypress, but you need some way to communicate a fin…

I’m pretty sure that also wouldn’t work now. Since idle keys don’t get their event handlers called any more, as soon as you release the macro key, the alt would be released. You could do alt-down, tab-tap, then send a OneShot alt, which ought to keep it pressed, but you’d still need a separate key t…

That’s what I was afraid of. Maybe I could combine a qukeys for something that is held longer on the one half, like bksp to become alt, and then use tab as normal. would this work?

You can have a macro that sets a flag, and then in your loop() (or if you use the plugin API, in beforeReportingState()), you inject Alt+Tab.

Wouldn’t this have the same key-down/key-up problem?

[image] n3f: Wouldn’t this have the same key-down/key-up problem? Nope. Here’s an - untested - attempt: namespace kaleidoscope { class AltTabber : public kaleidoscope::Plugin { public: AltTabber() {} EventHandlerResult beforeReportingState(); static uint8_t step; }: uint8_t AltTabber…

I know this is an old topic but I found its content quite useful as a new user. I actually went down the path @algernon offers and completed it to a tested attempt. I go more in depth here . For those searching for a working example, here is my current firmware Model01-Firmware.ino (11.3 KB) It us…

Alt+tab remapped... maybe tap dance?

Programming

fire January 29, 2020, 2:47pm 12

I played with something like this awhile back: "Just act normal" in a macro

Topic		Replies	Views
Alt+Tab, Ctrl+Tab & AltGr teething troubles	6	453	October 2, 2022
Can I change the function of modified keys, e.g. Alt+PgUp? Help and Getting Started	4	327	December 4, 2022
Hold down mods not working as expected Help and Getting Started	6	575	July 17, 2023
Alt, AltGr, and Mac/PC mode Model 01 Layouts	31	6994	December 13, 2016
Macros and modifiers, again Programming question	0	195	April 5, 2024

Alt+tab remapped... maybe tap dance?

Related topics