![]() Registered Member ![]()
|
I hide one layer and saved it. Then I closed the file and open again. I can still see two layers. Krita 4.1.7
Huion GT-221 PRO Windows 10
Linktree |
![]() KDE Developer ![]()
|
|
![]() Registered Member ![]()
|
If you have a saved image (without any other changes to it) and then hide a layer, Krita doesn't register it as a change (you don't get a * in the window titile) and the save button or save shortcut will do nothing since there are no changes. Is that what you are experiencing? If you change the layer visibility alongside other changes, it should work.
|
![]() Registered Member ![]()
|
Yes, that's what happening to me. I have a complete saved file. I just want to hide a sketch layer and save it. Toggling Layer Visibility only does not trigger asterisk beside file name.
In case if you want to see how it happens. -I made a file with 3 layers and saved it to test this. https://youtu.be/X24F1ty4W-c
Huion GT-221 PRO Windows 10
Linktree |
![]() Registered Member ![]()
|
This is really obnoxious. I've got a big file containing a lot of sub images it'd be REALLY nice to not have to change layer opacity back and forth to tell krita the file has changed so I can save it. (really if I press save it should just save regardless tbh).
|
![]() Registered Member ![]()
|
Personally, I like that it layer visibility doesn't register as an edit and also doesn't clutter the undo history, because for me usually it's more a thing I do temporarily as part of my workflow and not something I want to save permanently. I think this is a thing where people are pretty divided?
(Renaming layers, otoh, seems more like a thing that people want saved?) |
![]() Registered Member ![]()
|
Then just make it so that pressing ctrl + s ALWAYS triggers a save regardless of whether krita thinks there's changes or not.
|
![]() Registered Member ![]()
|
That's annoying when working with Transparency.
I used a background to see the image clearly but I want to hide it when I save it. I hope there will be better solution for this.
Huion GT-221 PRO Windows 10
Linktree |
![]() Registered Member ![]()
|
I think this area of behaviour (for layer visibility, renaming and other properties) is under consideration at the moment.
https://bugs.kde.org/show_bug.cgi?id=380437 https://bugs.kde.org/show_bug.cgi?id=394363 https://bugs.kde.org/show_bug.cgi?id=389876 https://bugs.kde.org/show_bug.cgi?id=389561 A crude workaround would be to add a dummy layer to the bottom of the layer stack and paint on it after making these changes so that a 'saveable change' would be registered and the the saved file would be as required. |
Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]