gTile@shuairan: fix terminal won't move after resize #544
Conversation
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
…ove after the resize of move_resize_frame. This fixes the issue with the terminal only resizing but not moving
rcalixte
approved these changes
Dec 22, 2023
|
This is an unmaintained extension. Please feel free to let us know if you'd like to take it over. Also, if there are any issues, please let us know so we can revert. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
#Motivation
gTile would resize but not move the terminal as described in #425
Fix
The metaWindow documentation for move_resize_frame describes this as a resize call. Moving after resizing seems to work for most the windows but not the terminal (which only seems to resize but not move).
By adding the move_frame call directly afterwards, this forces moving the terminal after the resize.
additional comments
This seems to be more of an issue with the Meta api. but this seems to work as a workaround solution