Hello,

From the looks of it text entry cursor in Plasma 5 is at least 30-40% bigger compared to KDE 4's. I am on Fedora 22 and I use 10 pt. Oxygen Sans/Mono fonts. In Konsole or Kwrite the new cursor cover the letter and at least half of line above it. It is a little hard to take screenshot of cursor but I can take a video if I am not clear enough.

Thanks.

It does feel a bit big at times.

Then again, it's simply keeping the same size as the other cursor icons.

And if we were to change its size, there's no good way to decide on what a 'proper height' for a text entry cursor is, as people have a vast variety of font sizes on their systems.

veqz wrote:It does feel a bit big at times.

Then again, it's simply keeping the same size as the other cursor icons.

And if we were to change its size, there's no good way to decide on what a 'proper height' for a text entry cursor is, as people have a vast variety of font sizes on their systems.

What were we doing in KDE 4 that we aren't doing in Plasma 5? How has user behavior changed in Plasma 5 which warranted such a change? It was fine in KDE 4. It feels weird when you have text cursor that spans two 10 pts font size lines.

Please use the delay feature to create a screenshot - the cursor isn't anything exceptionally huge here.

I think these are certainly bigger than what we had in KDE 4.

err.... are you talking about the I-beam cursor shape for the mouse pointer??

Code: Select all

kcmshell5 cursortheme


It's resolution dependent by default now (and I've two variants - 24/48 and 32/64 px)

=> Either your logic resolution is bonkers

Code: Select all

xdpyinfo | grep resolution


or you simply don't like the result => pick a hardcoded size.

Yes, I am talking about the I-beam thing. I have used all versions of Plasma and this seems to be a new thing in 5.3. Changing cursor size to 24 did help.

I don't see anything bonkers with my resolution. Do you?

Code: Select all

xdpyinfo | grep resolution
 resolution:    96x96 dots per inch


Depends - 96dpi is the "big windows resolution", but afair, the resolution factor is aligned to it (while it's rarely the actual physical resolution)

If the size was previously set to hardcoded 32 or 48 (or maybe even if just the 32/64 variant was selected, while that seems to be a bug to me), that's however irrelevant anyway.