Bug 412623

Summary:	Layer Hiding is not saved.
Product:	[Applications] krita	Reporter:	acc4commissions
Component:	General	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	ahab.greybeard
Priority:	NOR
Version:	4.2.7
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:

Description acc4commissions 2019-10-05 00:23:08 UTC

SUMMARY


STEPS TO REPRODUCE
1. Save the document with some layers.
2. Hide any layer. (Or make any layer 'visible'.)
3. It works, but Krita doesn't recognize the change in the document. If you save it and open it again, it returns back to the state where the layer visibility change has not been done yet. 

I have to make other changes to the document to 'save' the layer visibility changes.


OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Comment 1 Ahab Greybeard 2019-10-05 18:07:16 UTC

There are some actions that affect the on screen projection but don't mark the image as being changed. These have been noted in other bug reports but I can't find them. I remember that Tyson Tan was very keen to have layer visibility changes saved without the need to make other changes.

It must be one of the many things that are still being discussed and decided.

Comment 2 acc4commissions 2019-10-05 22:47:23 UTC

(In reply to Ahab Greybeard from comment #1)
> There are some actions that affect the on screen projection but don't mark
> the image as being changed. These have been noted in other bug reports but I
> can't find them. I remember that Tyson Tan was very keen to have layer
> visibility changes saved without the need to make other changes.
> 
> It must be one of the many things that are still being discussed and decided.

What is the reason why layer visibility changes should not be saved? I'm confused that it even needs a discussion;

Comment 3 acc4commissions 2019-10-05 22:49:10 UTC

It's just a regression(a huge one) from a user's point of view;

Comment 4 Ahab Greybeard 2019-10-06 06:10:45 UTC

Here's the 'original': https://bugs.kde.org/show_bug.cgi?id=389876

You can follow the duplicate links to read more about it.

*** This bug has been marked as a duplicate of bug 389876 ***

Comment 5 acc4commissions 2019-10-06 06:47:26 UTC

Thanks!