https://bugs.kde.org/show_bug.cgi?id=420568
Tiar <tamtamy.tym...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|crash |normal
--- Comment #4 from Tiar <tamtamy.tym...@gmail.com> ---
While lots of those issues are fixed now, there is still an issue that when the
resource is in the database but cannot be loaded for whatever reason, switching
to it won't do anything. It might look like the preset is selected but it will
still paint like the previous preset. (This behaviour is shown on the video
0:40).
I must admit I haven't checked if the memento safe assert still happens in that
particular instance, but I doubt it - there were lots of those asserts some
time ago but now I haven't seen them for a long time, so I would guess it's
fixed already.
Resetting the brush is fixed already, too, so the original steps to reproduce
don't lead to the bug anymore.
Possible steps to reproduce:
1. Put a bundle file into resource folder.
2. Open and close Krita.
3. Move the bundle to the bundles/ folder (I did it to get brushes in Krita 4).
4. Open Krita, try to select a brush from the bundle.
EXPECTED
Brush paints as it should.
ACTUAL
It paints just as the previous one.
--
You are receiving this mail because:
You are watching all bug changes.
