Inkscape 1.1.2 - Hackdot

Re:Inkscape 1.1.2 by chrismorgan on Sunday February 06, 2022 @08:35AM (#30232352)

I appealed to them in concrete terms at one point not long before the release of 1.0: either fix things for Windows, or keep on recommending the 0.92 series for Windows. There’s no denying that for the 1.0 release Windows was a second-class citizen. There’s no reason why they couldn’t then say: “look, 1.0 is available, and if you want the new features you can use it, but it’s considerably slower than 0.92 and the Windows theme is very badly broken so you’ll be stuck using the Adwaita theme which is extremely wasteful of space, so all up we suggest sticking with 0.92 for now; BTW talk to us if you’re interested in helping to improve things or sponsoring such work”.

[ Parent | on HN ]

Re:Inkscape 1.1.2 by pbhjpbhj on Sunday February 06, 2022 @11:32AM (#30234041)

Do you think all users would agree with you?

I used Inkscape on Win10 recently, and also on Kubuntu (21.04 a and 21.10, I think) and the experience was comparable.

I do not like the icon themes now, they're very low contrast and difficult to decipher for me so use the old, colourful icons I'm familiar with. Apart from that and one problem with a dialog not appearing until I selected the option a second time (the XML dialog), all worked well.

I think it's difficult, a x.0 might not be snappy, might even have serious issues, but there's not enough manpower resource to address everything at once, it's going to be incremental. Holding things back would negatively impact the momentum of the project IMO, but yes may benefit an individual.

[ Parent | on HN ]

Re:Inkscape 1.1.2 by chrismorgan on Sunday February 06, 2022 @10:15PM (#30239877)

Quite a few people have remarked on the performance problems. For the spacing thing, the use of Adwaita doubled the minimum width of things like the Fill & Stroke panel because of its excessive button padding, so that on my Surface Book (effectively 1500×1000) with the typical layout, I would end up with something like a 35–40% reduction in available canvas width (and maybe 10–15% for the height); but even the common resolution of 1920×1080 is going to suffer a fairly significant reduction in available width, compared to the Win32 theme.

But I couldn’t even properly switch back to the Win32 theme because of severe bugs that rendered it very problematic on all displays and basically completely unusable after a bit on any comparatively small high-DPI displays like my Surface Book’s. I don’t know if any of these issues have been fixed; I did try Inkscape 1.0 final briefly but decided it was still just too bad compared to 0.92. And now I’m back on Linux and so, like the Inkscape developers, don’t care all that much about Windows any more.

(https://gitlab.com/inkscape/inbox/-/issues/879 was my initial report, including explanation of some of the major Win32 theme regressions. Given the adjacent topic in this thread of GTK 4, the mention of overlay scrollbars in that thread points to a mess too; https://wiki.archlinux.org/title/GTK#Disable_overlay_scrollb... says: “as of GTK 4, the overlay nature of the scrollbars is part of the toolkit.” Ugh, GTK is obviously not interested in being a native look-and-feel toolkit if they deliberately remove the ability to control scrollbar overlayedness at the system level or in the theme. If you require the app to switch it on, it might as well not exist. Sounds like they’re continuing with the sabotage.)

[ Parent | on HN ]