Feature Request: TCP-based Remote Variable Modification for Single Sublayer Layout Adjustment

[xsphen]

Is there a way to modify only a sublayer? My idea is to achieve this by defining a sublayer as a variable + remotely modifying the variable value via TCP—this would allow us to change the binding logic of just a single sublayer (for example, altering the key-triggered ChangeVar winlayer=l_code to winlayer=l_browser), instead of switching the entire layer with ChangeLayer.

[jtroo]

I'm not sure that I understand the ask, more concrete examples with minimal configurations may help.

From my interpretation, seems like you could use switch to modify keys on an arbitrary layer, modifying its behaviour through TCP virtual/fake key actions.

[xsphen]

You're absolutely right — operating on virtual keys is far safer than manipulating variables directly. Therefore, my goal is to fulfill the following use case:
I have a set of default key mapping rules in the base layer, and I want certain keys in this default base layer to change their behavior automatically when the active window changes.
For example:
In the base layer, holding the Tab key switches to the l_tab layer, and holding CapsLock switches to the l_edit layer.
When using a browser, holding Tab automatically switches to l_tab_browser; when using VSCode, holding Tab switches to l_tab_code; in all other cases, holding Tab defaults to l_tab_default.

(defvar l_tab l_tab_default)

(defsrc
  tab caps 
)

(deflayermap (l_base)
  tab (layer-while-held $l_tab)
  caps (layer-while-held $l_edit) 
)

(deflayer (l_tab_browser)
    ...
)

(deflayer (l_tab_code)
    ...
)

(defvirtualkeys
  vk_browser (set $l_tab l_tab_browser)
  vk_vscode (set $l_tab l_tab_code)
)

External tools can trigger these behaviors using commands like:

{"ActOnFakeKey":{"name":"vk_browser","action":"Tap"}}

or

{"ActOnFakeKey":{"name":"vk_vscode","action":"Tap"}}

Of course, modifying the base layer directly could also achieve this goal. However, adding support for variable assignment would make the configuration far more flexible — enabling more combinations and reducing the overall length of the configuration code.

[jtroo]

Make your TCP integration do press only of vkeys, on application change release all others and press the new one (this can be built into vkey action to release others). Use vkey press state as a variable within switch cases.

[xsphen]

Got it, I understand what you mean now. Thanks!