I’m sorry that the first topic I create on Krita-Artists is about something that is not working as expected.
Is it a security problem? I would say NO!
It is a flaw, a beauty bug in my eyes. ![]()
(A workaround would be to fill the empty spaces with useful shortcuts) ![]()
Okay, here we go!
Trying last night to customize the toolbars “mainToolBar” and “BrushesAndStuff”, in Krita 4.4.3 under Windows 10, to my needs, the result was “unexpected”.
For a reason that is not clear to me, two of the four available “Expanding Spacers” are not “displayed visually”, but “in writing”, i.e. they do not fulfill their function as expected by occupying “space”, no, these two “Expanding Spacers” are displayed as words written out.
In this way, the elements to be separated are also “somehow” brought apart, but not as intended.
Since it was about 3 a.m., I decided to go to bed first to get to the bottom of it the next morning.
The following versions were tested
- windows 10:
. Krita 4.4.3 - Portable
. Krita 5.0.0-prealpha (git 7fbe819) - Portable
. Krita 5.0.0-prealpha (git c4e3b84) - Portable
. Krita 4.4.5 - Portable- SUSE Linux Tumbleweed
. Krita 4.4.3 (installed via package management)
. Krita-5.0.0-prealpha-607fca8-x86_64 (AppImage)
To see if this behavior made it into the upcoming Krita 5 release, I filled the toolbars in yesterday’s version, Krita 5.0.0-prealpha (git 7fbe819), as a test, and this display error exists there as well.
Then this morning I waited for the build of the latest Krita 5.0.0-prealpha (git c4e3b84) and tested it with the same result.
Oops, yesterday Krita 4.4.5 was released, just tested it and added it here - error still exists.
Afterwards I did the test on SUSE Linux Tumbleweed with Krita 4.4.3, installed via the package management YAST, also the same display error. Finally I downloaded the newest AppImage Krita-5.0.0-prealpha-607fca8-x86_64 and there it occurs too.
To show the above described display error I have created corresponding screenshots.
-
Expanding Spacer - Krita 4.4.3; Windows 10
-
Expanding Spacer - Krita 5.0.0-prealpha (git c4e3b84); Windows 10
-
Expanding Spacer - Krita 5.0.0-prealpha (git c4e3b84); Windows 10
-
Expanding Spacer - Krita 4.4.5; Windows 10
-
Expanding Spacer - Krita-5.0.0-prealpha-607fca8-x86_64.appimage; SUSE Tumbleweed
-
Expanding Spacer - Krita 4.4.3 (‘Standard-Installation’ with YAST); SUSE Tumbleweed
So that was it, it’s not an error that would prevent anyone but me from painting or resulted in the loss of work. And that’s only for the time that went into testing, researching and creating this topic.
If this requires a bug report, I hereby ask that someone do it for me - if it is required at all.
I do have a KDE community account, but unfortunately I’m not familiar with issue reporting on KDE, nor with Bugzilla (and the KDE bug tracking system (bugs.kde.org) doesn’t accept my “KDE-Invent-Account”).
I tried to read into it today, but due to my limited capability, I feel overwhelmed with it at the moment.
Michelist
Then I hope I haven’t overlooked anything, or made a gross mistake in creating my first topic.
I translated and corrected this text using the DeepL dictionaries. It is not machine translated.







