-
-
Notifications
You must be signed in to change notification settings - Fork 216
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(wm): add cmd to id layered apps
Users on Discord noted that Microsoft Office applications were not being handled correctly by the wm. After some investigation it was clear that this was because the application windows had WS_EX_LAYERED set. This had only been seen once before with Steam, and so a whitelist for layered applications was previously added to the codebase with steam.exe hard-coded, but this had not been exposed via the cli. This commit adds a command to allow users to specify layered applications which should be managed, and also renames the whitelist to reflect that classes can also be used to identify applications on the whitelist. A section has been added to the README to guide Microsoft Office users to guide Microsoft Office users in configuring komorebi to correctly handle Office applications with Word given as an example. This commit also renames the identify-border-overflow command to identify-border-overflow-application for consistency, while retaining the previous command as an alias to maintain compatibility with existing user configurations. It should be noted however, that those like me who are using the generated komorebic AHK library, will have to update any AHK function calls to use IdentifyBorderOverflowApplication(). resolve #124
- Loading branch information
Showing
9 changed files
with
84 additions
and
70 deletions.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters