Bug 395247 - specifc cursor resize icons
Summary: specifc cursor resize icons
Status: CONFIRMED
Alias: None
Product: Breeze
Classification: Plasma
Component: Icons (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: visual-design
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-11 13:46 UTC by David Edmundson
Modified: 2022-12-01 04:50 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Edmundson 2018-06-11 13:46:17 UTC
We currently have 
v-resize and h-resize which looks like <-> 

kwin master has just gained support for 9 specific resize cursors depending on which edge is being resized i.e |->  or <-|    gtk also uses this in their CSDs.

This is useful if you have two windows near each other so you know if it's resizing the left edge of one or the right edge of the other. 

These should be called: ne-resize, n-resize, nw-resize, e-resize, w-resize etc.
representing north east south west for the edge
Comment 1 andreas_k 2018-06-11 13:57:41 UTC
Ken I don't know how to draw mouse cursor icons but if you don't have time I can ping andreadelsa.
Comment 2 Nate Graham 2018-06-11 16:45:14 UTC
I worry that for example using |-> instead of <-> might visually suggest that the window is only resizable to the right.

For comparison, Windows and macOS both effectively use No Borders now (technically Windows 10 draws a single colored pixel, not sure that really counts) and use the standard double-arrow cursor for window edge resizing.
Comment 3 David Edmundson 2018-06-11 17:16:15 UTC
it could still look like |<-> if we wanted
Comment 4 Nate Graham 2018-06-11 17:23:04 UTC
Okay cool. Just wanted to share some feedback regarding single-headed vs double-headed arrows.
Comment 5 Justin Zobel 2022-12-01 04:34:29 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!