Replies: 3 comments 2 replies
-
Yea mutable variables would be difficult to implement directly. The Kanata runtime doesn't know everything about the configuration. E.g. aliases disappear and so do variables, as you mentioned. They just get turned into the values used in the keyberon layout. There are some pretty interesting things that can be done by using fake keys as variables and using switch/fork for conditional execution though. It doesn't satisfy all use cases but it does work for some. |
Beta Was this translation helpful? Give feedback.
-
Would this feature support changing variables from other apps (e.g., by sending a TCP message?) For example, you can define Currently you can only change layers driven by other apps |
Beta Was this translation helpful? Give feedback.
-
With the addition of the |
Beta Was this translation helpful? Give feedback.
-
Recently #490 was merged, and it got me thinking that the entire PR could have been circumvented if we were able to modify a variable on a keypress, and then use that variable in calls such as
movemouse
, of even have anif
statement similar to a fork that tests an expression and dynamically executes actions at runtime. Is this completely out of the scope of this project? I snooped around the code handling the variables and it seems like there would need to be major refactors to implement this.Beta Was this translation helpful? Give feedback.
All reactions