Steven Calwas

I downloaded the latest 1.3.0 alpha and ran it for over an hour in different scenarios. The offset problem persists, but it turns out is only one problem state of...

I apparently discovered the cause of the offset. Because fonts on a 4K display are microscopic, I scale the font size in Control Panel to 150%. If I reset the...

@MichelArendt Actually I'm investigating this issue right now. It's a nasty and elusive bugger.

Update: Two GTK merge updates address the issue of MyPaint not recognizing pen stylus: [#2458](https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/2458) and [#2469](https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/2469). The issue of the drawing offset is described in GTK issue [#734](https://gitlab.gnome.org/GNOME/gtk/-/issues/734). One...

@bramhoven The workaround is to set all monitors to the same scaling value--any value, it doesn't have to be 100%. If you can set both monitors to 200%, even if...

I've been going through the source code for tablet input recently and can verify that Wintab input is forced to absolute mode. Relative/mouse mode is not supported. Cheers.

The gtk3-demo axes test also exhibits this behavior, so it appears to be an upstream issue.

This issue is fixed in GTK merge requests [#2501](https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/2501) and [#2502](https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/2502).

The GTK project seems to put a low priority on updating its Windows support. I have four GTK merge requests, including the two linked above, that have been waiting two...

Update: My fix for this issue was just merged into the GTK+3 branch. (Merge of the fix into GTK4 is still pending.) GTK v3.24.26 was released a few weeks ago,...