After Mac Sequoia 15.o update some of the "window resize & moving" actions don't work anymore. These are the ones that I have identified so far:
• Maximize Window Right Half
• Maximize Window Left Half
• Maximize Window
• Resize Window to Top Right Quarter/Corner
• Resize Window to Top Left Quarter/Corner
• Resize Window to Bottom Left Quarter/Corner
• Resize Window to Bottom Right Quarter/Corner
Note:
Before bug reporting, please make sure you have tried the latest (alpha) version of BetterTouchTool and that you have already tried to restart your system :-). If you encounter a crash, please attach a crash log from the macOS Console.app from the "User Diagnostic Reports" section.
Describe the bug
A clear and concise description of what the bug is. Any bug reports that contain insults against me or my software will be deleted without warning (unfortunately this has become necessary to mention here).
FYI, after installing macOS Sequoia 15.0 and using Better Snap Tool version 1.9.12, "Native System Resizing," I get a shortened border around all my application windows. (see screenshot)
Same here!
Have been a beta tester for Sequoia and everything have worked as it should. But after the update to 15.0 all shortcuts that include the numerical keyboard doesn't work (which for me is Maximize Window, Move window to next monitor, Resize to left and right, and Corners).
BetterSnapTool version: 1.9.12
Do you maybe still have the native tiling enabled? BTT/BST's native integration only works if the native snapping is disabled in System Settings => Desktop & Dock
I don't see a setting for "native snapping" in "Desktop & Dock". What is it called? There is a "Tile by dragging windows to screen edges" which is already disabled (it says "window tiling requires 'displays have separate spaces' to be enabled").
My "Resize to Left/Middle/Right Third" (mapped to ⌥+1/2/3) are working. But "Maximize Window" (⌥+a), "Maximize Window Left/Right Half" (⌥+q/w) are not working. Thank you.
ah if displays have separate spaces is disabled you must use the classic snapping (in the BTT snapping settings). It should already do that automatically, but maybe there is a bug with this scenario