I am using a Lenovo Tab P12 with Android 13 OS and Krita 5.1.5
My question is about the Touch docker. The top three buttons are “file” “save” “save as”
The “save” button works fine but when I select the “file” or the “save as” buttons I get a blank window with no way to exit.
Any help would be appreciated.
That part of the touch docker doesn’t work for any of us. It’s a known issue. I’m not sure what the plans are for it.
I stopped using the touch docker by customizing the toolbars.
Do we have a bug report for this. I think it should be reported if not already
I’m looking at bug 462848.
Initially they disabled the docker and that caused a number of unwelcome effects so it was re-enabled but without any of its functions until it could be studied further.
I’m running 5.2.2. The docker is totally white and without function.
Thank you for that information, Sooz.
I wonder what the code for the Touch Docker looks like.
Or would that be a rabbit hole I don’t want to go down.
Basically, I wanted an undo, redo closer than a little icon at the top so the “file” and “save as” would not be buttons that I would need to use.
I’m afraid I don’t know anything about that but maybe @freyalupen can point you in the right direction.
The code for the Touch Docker is here : plugins/dockers/touchdocker · master · Graphics / Krita · GitLab
From what I understand, the Touch Docker was an experiment in using QML/QtQuick, which isn’t used elsewhere in Krita, so it became unmaintained. There are plans to look into using QML/QtQuick for mobile-friendly UI after porting Krita to Qt6, where it should be easier to maintain.
Well, I looked at the code and here is what I found:
The program opens a call labeled “void” where it accesses the code for “file” and “save as” and then accessed code to open a window. Windows is able to process these calls whereas android does not. I don’t know about linux.
Here we go down the rabbit hole:
The Z80 processing chip accesses 8 bit memory. However, it reserves a bit of memory for itself, let’s call it upper memory. Greedy programmers wanted to use the upper memory for themselves. They were able to plug in graphic bits in a row, row after row to form a picture on the screen. That was a tedious process. They decided to plug the graphic bits in a block of lower memory and port the whole block into upper memory. The processing for the new “program” was handled in lower memory, but you now had two programs running on the screen!
One program that handled opening and closing several programs on the screen was called Carousel that could move programs in and out of upper memory. Another program was Epson’s ValDocs or valuable documents that used the upper function keys on the keyboard. And there was Windows that did the same thing as Carousel. IBM came out with their Personal Computer loaded with Windows but IBM used “off the shelf” parts to build it. Other companies used the same available parts to build “look alike” pc computers and also loaded it with Windows. And the rest, as they say, is history.
What is needed in Touch Docker is a bunch of " If then " statements to determine which operating system is being used and open the “file” and “save as” part of the program instead of using the “void” code to open them.
Ah! fresh air. I’m not going down that rabbit hole again.
Off-Topic, sorry:
That were the times when we were young!
Look at me now:
Michelist