Bug 450366

Summary:	Drag and drop of text obscures the cursor
Product:	[Applications] kate	Reporter:	Cyrille Dunant <cyrille.dunant>
Component:	general	Assignee:	KWrite Developers <kwrite-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	christoph
Priority:	NOR
Version First Reported In:	21.12.2
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Cyrille Dunant 2022-02-16 08:59:51 UTC

SUMMARY

when drag-and-dropping text, there is visual feedback of the text being d&d but because the feedback is opaque, the cursor is hidden, and it is very difficult to place the text in its new location.

STEPS TO REPRODUCE
1.  write some text
2. select and drag
3. try to position it...

OBSERVED RESULT

it's very difficult to aim

EXPECTED RESULT

it should be easy. This could easily be achieved by making the feedback semitransparent.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Comment 1 Christoph Cullmann 2022-03-13 20:58:40 UTC

Hmm, for me this is already properly semi-transparent.

Comment 2 Cyrille Dunant 2022-03-13 21:02:52 UTC

(In reply to Christoph Cullmann from comment #1)
> Hmm, for me this is already properly semi-transparent.

Maybe this is due to drivers? this is X11, i915. placement is haphazard, too. If there was a way to disable the feature, I'd have a workaround...

Comment 3 Christoph Cullmann 2022-03-13 21:10:28 UTC

No, there is no switch for that.

Comment 4 Christoph Cullmann 2022-03-27 17:15:10 UTC

I will close this.
It works as designed, it is unfortunate that for your setup the translucent stuff doesn't work properly, but I don't see that we implement a second code path for this to workaround driver issues.

Comment 5 Cyrille Dunant 2022-03-27 17:53:18 UTC

(In reply to Christoph Cullmann from comment #4)
> I will close this.
> It works as designed, it is unfortunate that for your setup the translucent
> stuff doesn't work properly, but I don't see that we implement a second code
> path for this to workaround driver issues.

Fair enough. I still think these issues should be documented. Which is now done :)