not_IO@lemmy.blahaj.zone to linuxmemes@lemmy.worldEnglish · 1 month agodifferent design philosophieslemmy.blahaj.zoneimagemessage-square241linkfedilinkarrow-up11.17Karrow-down16file-text
arrow-up11.17Karrow-down1imagedifferent design philosophieslemmy.blahaj.zonenot_IO@lemmy.blahaj.zone to linuxmemes@lemmy.worldEnglish · 1 month agomessage-square241linkfedilinkfile-text
minus-squareprogrammerlexi@sh.itjust.workslinkfedilinkarrow-up14·1 month agoBecause it uses the XCursor format, which is a quite old standard. Getting apps to switch to a newer standard that has vector graphics is already hard enough. Getting them to do so without burning your GPU is basically impossible.
minus-squareflying_sheep@lemmy.mllinkfedilinkarrow-up4·1 month agoNo it doesn’t it just uses metadata compatible with XCursor themes, see e.g. this discussion. The fix was needed because the render code just used to have a maxScale: https://invent.kde.org/plasma/kwin/-/merge_requests/9176
Because it uses the XCursor format, which is a quite old standard. Getting apps to switch to a newer standard that has vector graphics is already hard enough. Getting them to do so without burning your GPU is basically impossible.
No it doesn’t it just uses metadata compatible with XCursor themes, see e.g. this discussion.
The fix was needed because the render code just used to have a maxScale: https://invent.kde.org/plasma/kwin/-/merge_requests/9176