Open
Conversation
joaomcarlos
force-pushed
the
feature/auto-zone-association
branch
from
d011bab to
de7c75d
Compare
Author
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi,
This adds the ability to auto-associate a window to a zone based on size/position within a tolerance of 6px.
If a window was not "placed" by the current running app, it wouldn't be tracked correctly. So, after a restart or a re-build, the window cycling functionality wouldn't work correctly.
This adds the ability to automatically track the windows with association with their correct zone, thus, everything will work as if you had just "placed" the window with the current running app.
What this is not: #13 Window affinity to zones (the ability for windows to have affinity to a zone so they move to the correct zone on layout changes)
A "normal user" won't see anything new with this change, other than the behavior being more consistent.
PS: I had originally wrote this description in a more detailed manner but GitHub saw fit to throw an error and I lost the text, so, this one is more straight to the point and less floral :D (and yes, i will cmd+a and cmd+c it before hitting the "Update comment" button)