Fix new layer creation on every client invocation#191
Merged
ErikReider merged 1 commit intoErikReider:mainfrom Dec 9, 2025
Merged
Fix new layer creation on every client invocation#191ErikReider merged 1 commit intoErikReider:mainfrom
ErikReider merged 1 commit intoErikReider:mainfrom
Conversation
Also fixes all the layers stacking in memory and showing again all at once when a new action is dispatched to the server. Removed useless GTK imports that shouldn't be used because of the headless nature of the client
Contributor
Author
|
seems like CI failed because of some required dep download failure, cant trigger a new run on my end. lmk if there's anything i can do |
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
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.
Also fixes all the layers stacking in memory and showing again all at once when a new action is dispatched to the server.
Removed useless GTK imports that shouldn't be used because of the headless nature of the client