https://bugs.kde.org/show_bug.cgi?id=506327

[email protected] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #5 from [email protected] ---
I encountered this as well, and it seems like the toolbar stops getting paint
events and gets loaded into a weird state. You can still click on the buttons
and get tooltips, however.

I think this bug might occur because toolbars are in a strange half-way state
when opening Krita, that is, you can see your custom toolbar docked at the top
of the window in the home screen, and then when you open a document, the
toolbar needs to be undocked and sent to its last floating position. If you
undock the custom toolbar before opening a document, the buttons appear again,
however, the move handles are gone and the toolbar cannot be moved again. If
you undock and redock the custom toolbar before opening a document, the custom
toolbar will get undocked to the last floating position after opening a
document, and the rendering and move handles are broken again.

My guess is that the "undock to last position" operation may be getting some
erroneous parameters, or at least that's the first place I would look, because
that's when the errors seem to start.

Regardless, I think a better solution would be to make it so toolbars are
"dockers" instead, that way you can dock a "toolbar" anywhere, not just on the
absolute edges of the window (which is why users end up making toolbars
floating in the first place, because they can't dock them where they want to).

KRITA VERSION
5.2.13

SOFTWARE/OS VERSIONS
Operating System: NixOS 25.11
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2
Kernel Version: 6.17.1-zen1 (64-bit)
Graphics Platform: X11
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 64 GiB of RAM (62.7 GiB usable)
Graphics Processor: AMD Radeon RX 7900 XTX

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to