Bug 409696 - Filter Wrap-around Corruption
Summary: Filter Wrap-around Corruption
Status: RESOLVED DUPLICATE of bug 406490
Alias: None
Product: krita
Classification: Applications
Component: Filters (show other bugs)
Version: 4.2.2
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL: https://forum.kde.org/viewtopic.php?f...
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-10 20:15 UTC by dillon.aron
Modified: 2021-07-27 10:43 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dillon.aron 2019-07-10 20:15:47 UTC
SUMMARY
Using the invert filter when in wrap-around mode and then moving the layer that was filtered cause the layer to be corrupted.

STEPS TO REPRODUCE
1. Create a layer with speckle/noise brushes
2. Duplicate the layer
3. Activate wraparound mode
4. Invert the new layer
5. Move the layer around using the Move Tool - at this point, the layer corrupts and displays incorrectly

OBSERVED RESULT
The filtered layer becomes a rectangular corrupted shape

EXPECTED RESULT
The filtered layer should remain filtered and moved over from its original position

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

ADDITIONAL INFORMATION
This issue happens on both my coworkers and my own machine. We reverted back to an old build we had (2.9.1) and the issue was not present in that build.
Comment 1 vanyossi 2019-08-23 23:59:39 UTC
In wraparound mode after invert if move tool is used, old image cache is used and inversion result is lost or corrupted.

setting to confirmed
Comment 2 Dmitry Kazakov 2021-07-27 10:43:54 UTC
The problem happens because the filters are applied to the visible area of the image. This behavior is intentional, though we could probable reconsider that.

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