This Week in Krita | August 5th, 2021

Develop Development news
1

Hello and welcome to a new “this week in Krita”! I’m hoping to resurrect this weekly update so that everyone can see all the cool stuff the Krita devs have done. Fixing things up for Krita 5 seems to be the focus this week. Things are looking good with 57 bugs closed this week and only 14 new ones. Seeing this kind of decrease in the bug count is really good to see!

It’s my first time doing this week in krita, but I hope the changes are clear for everyone. If anything described is confusing, please ask a question :slight_smile: .

New Features

Know Zero has been hard at work adding new functionality to the python API including Transform masks and basic manipulation of layer styles. It should be really cool to see what new plugins people do with it!

Crashes

Halla fixed a crash where if a brush tip didn’t exist (like from a bad import) Krita would crash. She also set a default brush in this case as well.

Dmitry has fixed a few crashes this week caused by:

  • Saving an image with trimming
  • when closing a gamut mask document
  • Moving a selection created with the magnetic selection tool

A crash when undoing/redoing colorize mask operations was fixed by Sharaf Zaman.

Bug Fixes

Halla fixed a bug where sometimes you wouldn’t be able to save using image split if the document had vertical and horizontal guidelines

Emmet O’Neill fixed a bug where adding a tag in the resource manager would fail if the resource was inactive.

Finally Know Zero fixed an issue where if you cancel an import of a layer style, it would still prompt for a name.

Performance and code cleanup

Eoin O’Neill has done some good work with the storyboard docker this week. There was an issue where the storyboard docker would be enabled/rendering (empty) frames even when not in use, which is now fixed. The storyboard docker should also be more responsive sometimes when editing layers that affect multiple scenes.

Laurențiu Nicola is a new Krita contributor that’s had more than a 5 changes this week including a lot of fixes for warnings when building Krita.

Those are the updates to Krita this week. There were also many backend changes that aren’t very user facing but help to make the code better and easier to work with. I hope seeing all the fixes can keep us excited for Krita 5. If you like what the krita team is doing consider making a donation at fund.krita.org. It helps out them a lot!

20 Likes
2

Thanks you very much for picking up the baton for this week in krita posts. :+1:t4:

1 Like
3

Hi, I find this kind of post absolutely interesting, I’ve been following Krita 5.0 maturing for quite a while and I’m so excited to see how cool will it be; I just have a couple of questions, where can anyone see that kind of information (number of bugs solved and number of bugs left) and given this kind of information, what is the forecast for a release of Krita 5.0? is it close to be released?

4

@Taiyou

Hello and welcome to the forum :slight_smile:

To see the bug reports, go to https://bugs.kde.org/
This is the formal bug reporting tool for all KDE applications. You’ll need to mainpulate the Search facility, which I always forget how to do, so I just look at the 7-day listings then find ‘krita’ in the long list. This does not include bugs that haven’t changed for more than seven days.

I believe that the 5.0.0-beta will be released soon for public testing and feedback.

5

There should be hope for a beta this week

6

We also post a link to our weekly meeting notes to the kimageshop mailing list. Those include a roundtable where everyone who is sponsored to work on krita, or who wants to participate tells the others what they’ve been doing.

7

Yup as @AhabGreybeard said krita uses bugzilla for its bug reports. Make sure you search with krita as a product or you will get all the bugs for other KDE software as well. Here is the weekly report on bugzilla.

I also looked at the krita commit message which show updates to the code from the developers. Although the descriptions can have a lot of technical terms so they may sometimes be difficult to read if you haven’t done some programming.