https://bugs.kde.org/show_bug.cgi?id=443875
Tiar <tamtamy.tym...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |NEEDSINFO
Resolution|--- |WAITINGFORINFO
--- Comment #5 from Tiar <tamtamy.tym...@gmail.com> ---
I fixed the main issue here:
https://invent.kde.org/graphics/krita/-/merge_requests/1116 which means, now
this workflow should work fine.
That means, if you follow this workflow:
- open the gbr file
- edit it
- save
- make sure the name is correct
- edit more
- make sure the name is correct
- etc.
Then you'll end up in this situation:
- your old brush presets would use the old brush tip (Ok, I'm not 100% sure of
that because there has been lots of sheningans with md5 sums recently, but last
time I understood that part of Krita, the assumption was, it should work. In
the worst case scenerio, all of the presets created in recent Krita 5.0 builds
should work, because they embed their tips)
- the brush tips chooser will only show you the brush tip with the changes you
made. So if you want to create a new brush preset, you only have access to this
tip with new changes.
- yes, the brush tip file will be named weirdly, "brushtip.0014.gbr" or
something like that, according to the version.
---
There are still three issues left, which for me seem a bit "maybe after Krita
5.0":
- the document is still marked as modified, despite just being saved (it would
be easy to fix but I would like to first know where standard documents are
marked as not modified before I fix it here...)
- if you open a version that is not the first one, for example if you open
"brushtip.0014.gbr", it will ask you to name the brush tip and the suggested
name is "brushtip.0014", not "brushtip"
- you can't simply overwrite over the brush tip file without making a new
version
Also something I noticed, but probably is not a regression - the "Auto" part of
spacing is forgotten before saving.
---
@David Revoy, please let me know if this compromise (main issue fixed, minor
issues left) is good enough to warrant removing "release_blocker" tag from the
bug report.
--
You are receiving this mail because:
You are watching all bug changes.
