Hey, thanks for quick reply!

actually, im not sure if I got the clue about toggle vs. 'momentary' switch action

i've tried to flash your Sample Keymap with Momentary Switch but with that pressing CAPS lock basically doing nothing - no any action happens - it seems that it just changing layer0/1 because with caps locked state L became a PageUP and > act as pagedown. But no any actions on a CAPS key like expected Caps. Should I put something on a Layer1 in that case?

as of my keymap - im using the default after compilation tmk_keyboard/converter/adb_usb

thanks again for your help!

PS. I also want to clarify that in my original message, when I mentioned “Layout #1/2,” I was referring to the system input sources, such as typing languages. Additionally, it was expecting system behavior for CAPS LOCK, which now requires me to press CAPS twice to change the language.

Insane look, love it

This post explains how AI is changing commercial art workflows by speeding up early drafts and communication, while still relying on experienced artists for final vision and quality. Instead of replacing artists, AI acts as a support tool that helps teams work faster and more efficiently, especially in structured, specification-driven projects.
That idea connects well to discussions around Pay for TOEFL exam. Just as AI can assist artists but cannot replace true creative skill, tools and paid resources can help with TOEFL preparation, but they cannot replace genuine language ability. Paying official exam fees and using proper study support strengthens credibility, while shortcuts undermine the value of the result. Real skill, whether in art or language testing, still matters most.

What are some tips to reduce hand fatigue while typing for long periods?

I’m using an Apple Extended Keyboard II with a mechanical locking Caps Lock key.

For a long time, I used it with an Arduino Uno ADB→USB converter based on MCJack123/ArduinoADB, and everything worked exactly as expected.

Recently, I switched to a Pro Micro (ATmega32U4) for size reasons and installed the tmk_keyboard ADB converter. After the switch, I noticed a critical difference in how Caps Lock behaves when used to switch keyboard layouts.

⸻

Expected / Previous behavior (MCJack123/ArduinoADB)

Caps Lock state directly reflects the active layout:
*Layout #1
→ press Caps Lock (key locks)
→ switch to Layout #2
*Press Caps Lock again (key unlocks)
→ switch back to Layout #1

In other words, layout depends on the physical Caps Lock state (locked / unlocked).

⸻

Current behavior (tmk_keyboard)

The layout only changes on every second Caps Lock transition:
*Layout #1
→ press Caps Lock (locked) → Layout #2
→ press Caps Lock (unlocked) → still Layout #2

*press Caps Lock again (locked) → Layout #1
→ press Caps Lock again (unlocked) → still Layout #1

So effectively:
   •   I must press Caps Lock twice to change the layout
   •   The physical Caps Lock state no longer reliably indicates the active layout

This is very inconvenient and error-prone, especially since I use Caps Lock exclusively for input source / layout switching.

⸻

Important note
   •   Regular Caps Lock behavior works fine in TMK:
   •   unlocked → normal typing
   •   locked → Caps Lock ON (LED on)
   •   The issue only appears when Caps Lock is repurposed for layout switching

⸻

Question

@hasu Is there a way in tmk_keyboard to:
   •   Make layout switching depend on the actual Caps Lock state (locked vs unlocked), or
   •   Restore the behavior where each Caps Lock state change reliably selects a specific layout?

Id appreciate any hints / configuration options.