https://bugs.kde.org/show_bug.cgi?id=402978

            Bug ID: 402978
           Summary: Fill Layer with pattern loads wrong pattern after
                    reloading image
           Product: krita
           Version: 4.1.7
          Platform: MS Windows
                OS: MS Windows
            Status: REPORTED
          Severity: minor
          Priority: NOR
         Component: Layer Stack
          Assignee: krita-bugs-n...@kde.org
          Reporter: glen.boy...@gmail.com
  Target Milestone: ---

SUMMARY
Creating a fill layer with a pattern then saving, closing and reloading results
in the fill layer having the incorrect pattern.

STEPS TO REPRODUCE
1. Create a new blank image
2. create a fill layer
3. select 'pattern' from the options and select any monochrome dither-style
pattern (the greyscale patterns seem to be unaffected)
4. Layer will fill with the selected pattern.
5. Save image.
6. Close Krita.
7. Reopen Krita and the image

OBSERVED RESULT
The fill layer will show the wrong pattern. In fact it looks a little bit like
it's merged 2 patterns together

EXPECTED RESULT
It should have the same pattern that was selected.

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

help->system info:
------------------
Krita
  Version: 4.1.7

Qt
  Version (compiled): 5.9.3
  Version (loaded): 5.9.3

OS Information
  Build ABI: x86_64-little_endian-llp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: winnt
  Kernel Version: 6.1.7601
  Pretty Productname: Windows 7 SP 1 (6.1)
  Product Type: windows
  Product Version: 7sp1

OpenGL Info
  **OpenGL not initialized**

ADDITIONAL INFORMATION
Krita appears to think it is displaying the correct pattern. If you open the
properties for the fill layer (F3) and select the correct pattern again and
click OK, Krita will not change the pattern - i'm guessing this is because it
thinks this is the currently selected one.

If I switch to another pattern and press ok then press F3 for properties again
and change it back to the correct one again, this time it will work.

This bug is also (for me) in versions 4.1.2, 4.1.5 and 4.1.7. These are the
only versions I've tested on.

Thanks for the amazing software though everyone. Much appreciated.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to