Bug 395124

Summary:	Edge Detect filter layer initializes incorrectly and requires manual refresh
Product:	[Applications] krita	Reporter:	SirPigeonz <GBirdboy>
Component:	Filter Layers	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	halla
Priority:	NOR	Keywords:	triaged
Version First Reported In:	4.0.3
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Video of Edge Detect Layer bug

Description SirPigeonz 2018-06-07 21:42:24 UTC

Sorry I can't attach test file. Reopening file fixes Edge Detect Layer so no point in example file :(

It's hard for me to explain it xD
To understand it, the best way is to reproduce the effect. Steps below.

Description:
If user creates Filter Layer with Edge Detect filter it displays wrong output of this filter, resulting with opaque black layer with edge from input layer.

Steps:
1 In empty file, add group with Pain Layer.
2 Paint shape on this Layer.
3 Create Filter Layer and apply Edge Detect filter to it.
4 Click "Eye" icon of this Filter Layer.
5 Click "Eye" again

Results:
Before step 4 and 5 Edge Detect displays different (preview?) output.

Expected result:
Edge Detect like output after step 5

Extra info:
I create layers like this also from Python and it has similar issues, although even worse. Layer is not displaying anything at all. I have to manually refresh it with step 4-5.

Comment 1 Halla Rempt 2018-06-08 08:18:04 UTC

Hm, no... I'm afraid I cannot reproduce. Could you perhaps do a screen recording?

Comment 2 SirPigeonz 2018-06-08 09:40:01 UTC

Created attachment 113146 [details]
Video of Edge Detect Layer bug

Shit that was my fault. I forgot to write that Layer with Shape and Filter Layer should be in Group!

Attaching the video. Sorry for error in the report.

Comment 3 Andrew Crouthamel 2018-09-28 03:40:35 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 4 Andrew Crouthamel 2018-10-29 02:11:03 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!