https://bugs.kde.org/show_bug.cgi?id=336607
--- Comment #12 from Friedrich W. H. Kossebau <kosse...@kde.org> --- @aguzinski Hi (and Happy New Year). Thanks for going the extra miles to come up with a patch to solve that issue with the missing support for non-blinking cursor. While I had that bug in the back of my mind, my memory also was that there had been some unresolved discussion about what to do for the non-blinking cursor rendering when it comes to the insertion state cursor: the shadow cursor marking the same spot in the non-input receiving half (char or values) would be only hard to distinguish (1 pixel line width vs. 2 pixel line width) from the active cursor. But this bug report does not have any related comment, so it might have been some other place or my memory just made this up from other similar things :) In any case, you are triggering me to revisit this problem now. Having the cursor rendering the inverted symbol is actually also an improvement for anyone (and adds consistency with text cursors in other apps). Perhaps this was different at the time when I wrote that logic, I think I tried to be consistent at the time as well :) Seeing your patch I assume that the mentioned issue for the insertion cursor is less grave and having a non-blinking cursor at all is already an improvement (and not affecting any people who prefer the blinking cursor). So fine with me to just support non-blinking cursor for now by just drawing the current cursor shape (updated with color-inverted data). Both things should be added in the next days and be part of the planned 0.26.5 release (so far a mere translations update) in the second week of January 2021. Now, any ideas how to approach the non-blinking cursor in the insertion variant? -- You are receiving this mail because: You are watching all bug changes.
