v0.2.2-preview.1
Pre-release
Pre-release
This is a preview release for v0.2.2.
In addition to the fixes from -preview.0 (#39, #30, and #52), it addresses the following:
- fixed old app_versions persisting in saved configs
- when saving config, a concise toast message is shown instead of verbose alert
- #49 - Handle multiple monitors with different aspect ratios -- THIS IS A BIG ONE:
- It required a big change to the config file format, that should facilitate new/advanced features going forward
- Instead of a flat config, fields are grouped into
grid_config,style_config, andbehavior_configentities - These new entities are stored in lists, so you can have multiple of each (currently only multiple grid_configs will have any effect)
- These entities have a
namefield, for referencing elsewhere in the config
- Instead of a flat config, fields are grouped into
- The new config field
screen_assignmentcan take the following values- "single": preserves prior behavior; the first entry in
grid_configswill be applied to all screens - "auto": the first
grid_configwill be applied to screens with a horizontal aspect ratio, the second will be applied to screens with a vertical aspect ratio- this is the default, and should provide the quickest, easiest solution to the direct issue of #49
- a list of strings: these will map each screen to a
grid_config, specified by name (a new feature; I will make an issue for it)- e.g.
screen_assignment: [qwerty, qwerty_small](assuming you've given those names to your grid configs) - I will add a facility soon so you can easily see screen numbers, for now, you may have to trial and error a bit if you have 3+ monitors
- e.g.
- "single": preserves prior behavior; the first entry in
- It required a big change to the config file format, that should facilitate new/advanced features going forward
- For visibility: You can now map different configs to each display you have connected (see directly above)
Usage notes:
- mouseless should automatically migrate your prior config on startup. Don't delete your backups, though! Given this a preview release, it's possible you may have to revert to your prior config if there are further changes or reverts
- The new default config is attached (or will be loaded if you don't have a
config.yamlpresent), and has both a horizontal grid config and vertical grid config defined - There is no gui functionality yet for editing the additional grid_configs
- Full validation is not yet implemented for the new config. So be careful with your config editing! Namely, ensure that the
_configslists are not empty, and that any strings in ascreen_assignmentlist actually have agrid_configwith that name (should fallback to first grid_config entry if not)
Testing it out and providing feedback before/by Monday is definitely appreciated -- a big thank you to anyone who does!! 🙏
Enjoy! 🚀