On Wed, 2017-12-06 at 02:14 +0100, Eduard Braun wrote:



Am 06.12.2017 um 01:59 schrieb Eduard Braun:
Am 30.11.2017 um 14:24 schrieb Tavmjong Bah:
Hi,

If you've got a high DPI screen, please test the High DPI canvas
branch:

	https://gitlab.com/inkscape/inkscape/tree/hidpi_canvas
	https://gitlab.com/inkscape/inkscape/merge_requests/137

There are a couple of minor problems that I know about (see merge
request). If no other ones are found, I'll merge the branch in the next
week.

Thanks,

Tav

Hi Tav,

I finally got around to do some testing on Windows 10. I'm attaching two screenshots with display scaling set to 100% and 150% respectively.

Some observations in no particular order:


Excellent!


I'm not sure I understand what you are saying. The arrows should have twice the number of pixels in both directions on a high DPI screen. They will be slightly blocky as the arrows are defined by bitmaps (the circles/squares/diamonds are programically generated so they are not blocky).


See below.


Yes, that's a problem I don't see how to fix.


Per monitor scaling works with Wayland but not X11 (at least with the simulated test monitor setup).

Let me know if there is anything that might need some additional testing (unfortunately my default display setup uses 100% scaling so I can not do "fly-by-testing") or if I can provide any additional information.

Best Regards and thanks for the great work on this so far,
Eduard


OK, slight correction: I just retested with 200% DPI scaling again (see attached):

GTK on X11 only does discrete steps. GTK under Wayland has experimental non-integer scaling which I believe works by integer scaling up by a scale factor greater than needed and then scaling down to the desired resolution.


This is similar to what I saw with Guide handles. I'm not sure how to fix this... We suffer from multiple ways of doing the same thing. The handles should just be the same canvas items as, for example, that the node tool uses... but they are not.