Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Device actions #1099

Open
mondalaci opened this issue Jan 17, 2025 · 1 comment
Open

Device actions #1099

mondalaci opened this issue Jan 17, 2025 · 1 comment

Comments

@mondalaci
Copy link
Member

This is the firmware-side issue of UltimateHackingKeyboard/agent#2502

A new key_action_type_t value has to be added for special actions. For clarity, it'd make sense to add one id for connections and another for the other special actions, which are expected to be extended later, but if we're short on key ids (assuming some bits of this byte are used in the RAM for other purposes), feel free to use a single, shared key_action_type_t value.

It'd be nice to visualize the empty/nonempty connection slots by showing the empty ones with half the brightness of their color when functional backlighting is used. (I'll extend the default configuration to map the "switch to connection 1", "switch to connection 2", ... actions to neighboring keys of the Fn2 layers.)

The new functional key color for special key ids must also be added.

@mondalaci mondalaci changed the title Special actions Device actions Jan 21, 2025
@mondalaci
Copy link
Member Author

Let's call these actions device actions according to the related Agent issue.

I suggest using the first 20 values for host connection slot ids and for the rest of the values, we could start from 255 and keep decreasing. This way, should we ever want to extend the 20 connection slots, it'd be easy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant