I tested the build https://yadi.sk/d/aPP0OEDRdUt0Mw and this is my test result:

The touch docker appears to work fine on my SP2017, but the other QML windows (the open/save file dialogs) doesn't respond to the stylus

Fix debug on openGL ES (not published, 0004-Fix-debug-on-openGL-ES.patch)

Updated patch for master

Upload the correct patch

The question is: should we change the default behaviour to RoundPreferFloor instead of trying to keep the old behaviour by using Round? I feel like RoundPreferFloor would be more useful to users who doesn't want to enable fractional scaling (but that will probably be the minority if we can enable fractional scaling by default).

Moved some code from the converter to the canvas.

In D20097#448006, @dkazakov wrote:

Speaking truly, I don't understand, what bug this huge refactoring is intended to fix. Please list the problems you are trying to resolve.

Right now the patch introduces at lease two huge regressions:

1. Zoom with mouse wheel and Ctrl+Space centers around wrong point.
2. Rotation with Shift+Space center around wrong point and drifts from place to place (some rounding issues).
   
   The main point, I don't see what problem we are trying to solve?

In D8543#447164, @vanyossi wrote:

Could not update this revission as it is not mine. Im continuing the work on this here https://phabricator.kde.org/D20423

• Softness Controls alpha borders
• Strenght controls how soon dark pixels clip to black
• Pixel brushes work as normal
  
  Missing
• save settings doesn't work

• Starting to convert more stuff to use device pixel
• Beginning to differentiate between device pixel and logical pixels

Add comments and updated 3rdparty/README.md

That bug should be fixed with R37:331beffd5332.

See https://bugs.kde.org/show_bug.cgi?id=405796#c4

After last night's test, I can say this is not the fix to the pyqt situation on Windows.

In D19807#432248, @yurchor wrote:

In D19807#432245, @woltherav wrote:

I'm a little skeptical about 'an hsv filter' as that would be verbalized as 'an hatchesvee filter', and we also talk about 'a human', 'a hatchet', 'a house', 'a hamlet' and not 'an human', 'an hatchet', 'an house'.

@rempt do you have an idea?

The English Wikipedia uses "an":

https://en.wikipedia.org/wiki/HSL_and_HSV#From_HSV

I think it's because it begins with /eɪtʃ/.

I see that you've already committed this but unfortunately it is just broken on Windows. Running config definitely isn't how one would be able to build openssl on Windows.

I agree you should make a separate define for use with OpenGL-ES-only environments. OpenGL ES is not limited to Android after all.

• Should I still remove Chocolatey, if it's very similar to Homebrew on Mac?

Though having the CMakeLists.txt doesn't mean they really support CMake build and probably nobody knows what would happen if you try to use it with the mingw-w64 native toolchain...

Both libraries seems to contain a CMakeLists.txt file. If they do support CMake there is no reason to not prefer it over using the autotools build.

In D18692#404662, @citelao wrote:

Does this make sense?

In D18710#404556, @citelao wrote:

I would like to mention the Shell extension for KRA previews here. I notice that my Store-version--created files have a preview, and my other (older) files don't.

Is the shell extension bundled with the Store version, or are previews automatically saved for it? I'm happy to update the diff appropriately.

See https://docs.microsoft.com/en-us/windows/uwp/porting/desktop-to-uwp-behind-the-scenes#file-system

In D18407#397873, @rempt wrote:

• Can it be made to save as Zip64 only when the file doesn't fit in a typical zip file?

Not easily: we cannot predict exactly when a file will become bigger than 4 GiB from the size of the image in memory.

A few things: