Hi, I've been having a docker issue since I started using Krita, which is that when I drag one to relocate it, it works just fine up to the highlighting of the selected drop place, until I release it. Then, about 98% of the time (no exaggeration here), it will either snap back to where it was before I picked it up or it will tab itself to another docker of the same type (for example: tools with tool options or advanced color selector with color sliders).
So far, I've only seen one or two reported cases of this happening, and they didn't answer in the slightest to what or why Krita does that to certain people. The most I've gotten out of them is a vague direction towards Qt having issues with my computer, but I have no idea how that works and I surely don't want to mess it up even more by fidling in something I don't understand.

However, roaming through my system files, I came across Krita's Workspaces folder, containing a couple .kws files, that I'm assuming store which dockers are present and where they are.

Code: Select all

<Workspace name="workspace name" version="1">
    <state><![CDATA[AAAA/wAAAAD9AAAABAAAAAAAAADRAAADqfwCAAAABvsAAAA (a loooong string of characters) //AAAAAAAAAAA=]]></state>
    <settings>
        <param name="palette" type="string"><![CDATA[palette name]]></param>
    </settings>
</Workspace>

I can see that this state tag seems to hold the different information about the dockers.
If I could force Krita's hand a bit and edit the workspace in a way that bypasses my broken drag-and-drop, it would be really awesome.
Is there any way I can make sense of what this or that string of characters represents, or is this information unavailable to the public?

I would greatly appreciate some insight on the workings of Qt, if it is at all in fault here, and what's going wrong with it, as well as some information on that character string in the .kws workspace files.

Thanks in advance,
A fellow Krita user with an uncooperative workspace

And just in case this would turn out to be of relevance to my problem, I'm running Windows 10 on a 64-bit fairly powerful laptop, and haven't meddled around in a significant way with my system files.

We don't have any special code for the docker system, it's all done by Qt itself... I don't have problems like you describe, but maybe, after twenty years of working with Qt and Qt-based applications I'm just used to it! And yes, the state tag stores the state of the dockers, but that's an opaque binary blob that's impossible to edit by hand. I'm not sure why the Qt developers decided to use that instead of something readable, but it's, again, not something we can change without hacking Qt.

Alright, looks like I'm fighting a losing battle, then.
Still, thanks for the insight!