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

Hi, @tusooaw and @lsegovia!

The bugs Alvin reported are fixed in this version. As for item no. 4 in my previous comment, it only works if I use WinTab as the source API. Windows Ink still doesn't work.

I'm on Surface Pro 4/Windows 10 and everything goes well except for (2):

Hi, @alvinhochun and @lsegovia!

1. Works correctly. (Although I get this bug a lot more in MacOS.)
2. Works correctly.
3. Works correctly as well.
4. Doesn't work on my machine. Verified by keeping a browser tab open besides Krita and testing press-and-hold opening the context menu.
5. Works correctly.

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

Color smudge was fixed to work a lot better in 4.1, so this can be closed :)

I still find that a bit scary... I think we probably should just use temporary files.

Hi @rempt, I looked into this today a bit as you mentioned it yesterday and it's indeed quite depressing on macOS.

We still have problems on OSX with this approach. On OSX shared memory segments have a very small default max size.

https://docs.krita.org/Smart_Patch_Tool This now needs screenies.

Moved this to the testing board.

In T1625#98082, @woltherav wrote:

1. If you have a groupLayer, and you wish to addChild() then the API asks two nodex, the first as the node to add, and the second as the node to add it above. If your group is empty...

1. If you have a groupLayer, and you wish to addChild() then the API asks two nodex, the first as the node to add, and the second as the node to add it above. If your group is empty...

We probably should use this:

Okay, so the above is a docker with a bunch of odds and ends scripts.

And I see there's no KoColor api either. Or a way to change the current foreground color. Let alone something that can chuck the color through the displayviewer...

Tested here and I didn't have the outline offset issue, and I couldn't reproduce the infinite recursion issue (built with Qt 5.8.0).

It sounds like this copy/paste issue is maybe specific to my build or windows OS. Not sure if the official builds will have this problem. It sounds like it is working alright on Dmitry's boxes that he is developing it on.

not sure if we are still putting comments in this ticket...

Fixed now! :)

Okay, so after some testing here, it seems that this causes artefacts when used with a low opacity on 8bit... 16bit is of course unharmed by any of this... Maybe @Deevad was right and we need to consider if we can somehow get the mixing algorithm to work on 16bit, though the last time I attempted this by converting the temp_dev to use a 16bit colorspace, it didn't seem to work.

Wolthera mentioned this, but the pattern tool option has nothing in it. If we aren't going to have time to get it working, it should probably be hidden.

When editing vector nodes directly on a line, it has some sporadic behavior... see video

Reposting the bug that I mentioned elsewhere

When opening a Svg - resize to image size jumbles up the image.
to reproduce,

Alright, this is the most complicated SVG I have:

1. SVG loading issues.

1. svg quality bugs

• In the Select Shapes tool, the opacity slider starts relatively uninitialised: It doesn't prepend opacity, nor is it set to the shape opacity.
• when you have a semi-opaque shape and it has markers rendered, the fill of the markers is more transparent than their stroke. (this also counts if the stroke has a semi-opaque color)
• Are Global Coordinates and Uniform Scaling implemented? If so, can we have a tooltip explain what they do? Toggling them is inobvious.
• Pattern fill should probably be disabled until it's finished.
• Changing the foreground color changes the stroke, but changing the backgroud color does not change the fill...
• When drawing a path with the path tool with 'fill->foreground and stroke->none', the stroke is still rendered as filled with the foreground color, aswell as set to the curret brushsize, but the fill color widget isn't shown.
• Similarly, the polygon, straight line, polyline, circle and rectangle tools have the stroke always set despite the configuration, and the stroke never takes the current brush size.
• Is there any reason why the stroke width is snapping to certain values? Is it set to render svg px?
• The stroke fill in the freehandpath/pencil tool doesn't do anything. Linestyle does work.
• When attempting to change the markers, I got a sigkill, god knows why:

 Program terminated with signal SIGKILL, Killed.
The program no longer exists.
(gdb)

Okey, first bug :3

Dmitry declared this testable yesterday, so lets add the bugs here. :)