[needs testing] First testing packages for the lager-based brush editor

[freyalupen]

It was mainly a rewrite of the code to be easier to work with, which could lead to some UI/UX improvements later on. For now everything should be essentially the same.
So the goal of testing is to test every unique brush option of every brush engine and make sure everything still works correctly. If something doesn’t work as expected, please report it. And if you thoroughly test a brush engine and everything does work as expected, it’s helpful to know that as well.

[karemuvar]

Will this mess with the existing settings and brush storage? I lost brushes in the past when moving up the versions.

[Michelist]

It should not happen, but, of course, something can always go wrong. That’s why I can only repeat again and again: “People make backups. Of your work, your settings and of course also of your resources, like the brushes for example!”, who uses Krita to earn money with it, should not necessarily use this version on the system and use a second PC for it.

Michelist

[SirPigeonz]

If you want to be safe (even when moving to new version from stable build to new stable build). Make a copy of your Krita resource folder or folders - if you use a non-standard location for some of your resources.

Then if something will go wrong, you will just remove it and paste back-up version
It’s also a good idea to not test on existing files. If you want to test something with an existing file, just make a copy first (in folder not with Krita).
If you do the above steps each time, when using test-builds or moving to a new stable release, you will be safe

It’s a good practice because even a stable release can have some nasty bug that slipped developers and beta testers.

If it happens tho, keep your files and report it as a bug. Sometimes script can be created to fix broken files. (Actually it happened once and somebody made script to fix affected resource files)

But please help developers by testing and reporting, it is really great help, really appreciated and important work that devs can’t do themselves!
More eyes are always better!

[Michelist]

There are other ways too, to create a safe test-environment

Under Linux, you can work with AppImages and create a home directory for every AppImage, even better would be separation via different user-accounts, there 100% separation is given.
Under Windows, you can create more than one user-account, and achieve a 100% perfect separation of every installation in its own account.
In the link at the end, you can find a description by me on how to start and use several Krita-Instances from one user-account. For instance, on my PC I often have more than one instance of Krita running, one for my own things, and one or more additional versions for being able to help here in the forum. This way I’m able to check issues on different branches, like release, plus, next, or a test-version like this one instantly.

Here is the link:

Want to try Krita 5 Beta

You can also run the version of Krita to be tested, after you have created a new user account, from your standard user account. If you use the command “runas /user:NEW-USERNAME” with a shortcut, or start the shortcut to the Krita installation of the new account each time by right clicking on the shortcut and selecting the menu item “Run as different user…”, where you then enter the name and password of the new account each time. For this I have set up shortcuts that pass this command as a param…

There is also a screenshot where you can see seven different versions running simultaneous on my monitors.

Michelist

[karemuvar]

@Michelist

Under Windows, you can create more than one user-account, and achieve a 100% perfect separation of every installation in its own accoun

That is really a hassle to do really. I would not change to another user to test something.

I looked am the link but I am finding it confusing. Are you recommending using a new account and run it under or are you recommending using the new account’s folders and still run it under the main user’s real environment?

Is there a way to define all these necessary folders without needing to create a new user given sometimes these users require admin permissions to create.

[Michelist]

First, you need the permission to create new accounts.
Next, each installation needs an account.
But later, you can run all of them under your account, if your account is granted the permission to run these Krita-Instances. To run this comfortably, you have to create links for each Krita you want to run from your account, in these links you can save the credentials needed to start the other Krita’s.
I manage all of them from my main account, the only time-consuming thing is the initial setup of this configuration. If I need another Krita, I double-click the prepared link and it starts.

Michelist

[dkazakov]

Hi, @freyalupen!

I think I have fixes the issues you reported

When loading the default Spray brush “spraybrush” (using the +), there’s SAFE ASSERT (krita): "data" in file C:/dev/env-4-lager/krita/plugins/paintops/libpaintop/kis_brush_option_widget.cpp, line 109.

I think I have fixed that by fixing the preview

The Spray engine’s Spray Shape width/height previously only went to 100% proportional, now it goes to 1000%. I’m not sure there’s any problem with that, though.

Yes, I increased the limit. It makes the engine a bit more flexible

Logged at startup is kf5.ki18n: Trying to convert empty KLocalizedString to QString. x6 from some placeholder i18n("") s in MyPaintSensorPack.cpp

Fixed

using a Sketch brush with the drawing angle sensor prints many krita.general: KisPaintInformation::drawingAngleSafe() DirectionHistoryInfo object is not available .

I cannot reproduce the issue. It is either fixed or I need better instructions