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
Allow the user to create pre-defined Grids to define custom window snapping areas. The size of the Grid should be up to the user. Check Lasso application for reference.
The user should also be able to:
Snap windows by holding Fn + drag the window to a slot (of course this shortcut should not be customizable)
Move windows within Grid slots using shortcuts (new commands)
For example, in a 3x3 Grid, by pressing Fn + Left while focusing the window 1-3 (top-right) would move the window to the 1-2 (top-middle) position
Open question: Should the window 1-2 move automatically to 1-3, once 1-3 moves, i.e. exchange slots? Or should them be stacked in the same slot?
Create shortcuts specific to the Grid
Open question: Does it make sense to keep the "global" ones (as long they don't conflict)? Like shortcuts to move windows
Enable/disable Grids using shortcuts (new command)
Only one Grid can be enabled at time
Requires remembering the window original size/position in order to revert it once the Grid is disabled
By combining these last two items together, it would be possible to have advanced combos. For example:
Fn + 1 (Enables Grid 1)
Fn + Left (Supposing I didn't like the result, I go on and...)
Fn + 2 (Enables Grid 2)
Fn + Left
We can think of it as an advanced - yet intuitive - toggle command, since, as I user, I'm choosing specifically which will be the next state instead of cycling through every intermediate one.
Nice to have:
Create a Grid by copying another Grid
Toast notification (or any other kind of visual feedback) to indicate the new enabled Grid
Open question: How to identify Grids? Giving them a name, generating them an icon, showing the preview for the entire Grid (personally like this one) etc
Remove the pre-defined shortcuts commands and add them back as pre-defined Grids. For example: 1x1, 2x1, 2x2, 3x2, 3x3 etc
By implementing this feature, Loop would have the ground work for implement yet another amazing feature: App Grid (similar to App Layout in Rectangle Pro).
Screenshots
No response
Additional Context
Currently users are restricted to only a handful of "grids" and sometimes they aren't enough, given a large screen or whatever the reason is.
Currently available "grids"
Loop has the awesome Custom command which allow users to create pretty much any grid they want, but it's also limited when they have different screen sizes. Let's say a MacBook Air and a large monitor.
Final Checks
My issue is written in English
My issue title is descriptive
This is a single feature request (multiple feature requests should be reported individually)
I can help with the improvement or development of this feature (tick if you can help)
The text was updated successfully, but these errors were encountered:
Feature Request Description
Allow the user to create pre-defined Grids to define custom window snapping areas. The size of the Grid should be up to the user. Check Lasso application for reference.
The user should also be able to:
By combining these last two items together, it would be possible to have advanced combos. For example:
We can think of it as an advanced - yet intuitive - toggle command, since, as I user, I'm choosing specifically which will be the next state instead of cycling through every intermediate one.
Nice to have:
By implementing this feature, Loop would have the ground work for implement yet another amazing feature: App Grid (similar to App Layout in Rectangle Pro).
Screenshots
No response
Additional Context
Currently users are restricted to only a handful of "grids" and sometimes they aren't enough, given a large screen or whatever the reason is.
Loop has the awesome Custom command which allow users to create pretty much any grid they want, but it's also limited when they have different screen sizes. Let's say a MacBook Air and a large monitor.
Final Checks
The text was updated successfully, but these errors were encountered: