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

Enable complex modifications file/group to be disabled based on conditions #4023

Closed
gdanov opened this issue Nov 22, 2024 · 4 comments
Closed

Comments

@gdanov
Copy link

gdanov commented Nov 22, 2024

I use custom dvorak complex modification file that works great, but when using UniversalControl (mac's mouse & keyboard control my iPad), the keyboard input is a mess — does not match neither the dvorak mapping, nor the physical keyboard.

The way I understand documentation, I have to add the same app exclusion rule to each and every modification in the "manipulators" array and this is overkill and ugly.

@tekezo
Copy link
Member

tekezo commented Nov 23, 2024

Wouldn't it work to use profiles?
https://karabiner-elements.pqrs.org/docs/manual/operation/profiles/

@gdanov
Copy link
Author

gdanov commented Nov 23, 2024

I don't see how. Can I enable/disable profile based on the current frontmost application in which I'm typing?
Effectively I need to disable all mappings when my focus is on specific app.

@tekezo
Copy link
Member

tekezo commented Nov 24, 2024

Yeah, if you want to change behavior based on the frontmost application, profiles are not suitable.
For now, the only way is to insert frontmost_application_if into all the rules.

here have been similar requests, so I’ll address this at some point.

@gdanov
Copy link
Author

gdanov commented Nov 24, 2024

thanks

@gdanov gdanov closed this as completed Nov 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants