You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I have looked through the json schema document and the documentation and can not find any information on setting the Monitor Index Preference values to map specific monitors to "rectangles" so their assignments don't migrate.
Expected behavior
To be able to configure the monitor index preference rectangles as part of the "monitors" key in the json config file.
Operating System
OS Name: Microsoft Windows 11 Pro
OS Version: 10.0.22621 N/A Build 22621
komorebic check Output
KOMOREBI_CONFIG_HOME detected: C:\Users\gamaliel.masters\.config\komorebi
Looking for configuration files in C:\Users\gamaliel.masters\.config\komorebi
No komorebi configuration found in C:\Users\gamaliel.masters\.config\komorebi
If running 'komorebic start --await-configuration', you will manually have to call the following command to begin tiling: komorebic complete-configuration
Additional context
I am still running key-bindings through AHK as I have not yet migrated them, but I don't think it applies to this issue.
The text was updated successfully, but these errors were encountered:
This commit adds an "monitor_index_preferences" key to the static config
schema, which was missed during the initial rollout of the static
configuration files. To help with testing, these indexes have also been
exposed on the State struct.
resolve#522
Describe the bug
I have looked through the json schema document and the documentation and can not find any information on setting the Monitor Index Preference values to map specific monitors to "rectangles" so their assignments don't migrate.
Expected behavior
To be able to configure the monitor index preference rectangles as part of the "monitors" key in the json config file.
Operating System
komorebic check
OutputAdditional context
I am still running key-bindings through AHK as I have not yet migrated them, but I don't think it applies to this issue.
The text was updated successfully, but these errors were encountered: