SUMMARY Spectacle shows a hand cursor when over a draggable Rectangle Region. As a minor UI tweak, it could change to show the "closed hand" cursor when said region is being dragged. I am not sure if this is documented in or goes against any KDE Human Interface Guidelines, it was just behaviour I observed from other applications and noticed that Spectacle does not do this. STEPS TO REPRODUCE 1. Create a Rectangle Region when taking a screenshot/screencast. 2. Drag this region. 3. The cursor does not change when the region is being dragged. OBSERVED RESULT Spectacle shows an "open hand" cursor when a Rectangle Region is being dragged. EXPECTED RESULT Spectacle could show a "closed hand" cursor while a Rectangle Region is being dragged. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.3.1 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Graphics Platform: Wayland ADDITIONAL INFORMATION
Can reproduce. Operating System: Arch Linux KDE Plasma Version: 6.3.1 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.3-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7600K CPU @ 3.80GHz Memory: 23.4 GiB of RAM Graphics Processor: AMD Radeon Pro 580X Manufacturer: Apple Inc. Product Name: iMac18,3 System Version: 1.0
It's actually supposed to do that already and did for a while, but it seems that something about dragging is a bit broken on Wayland.
Can reproduce this one with today's git master.
The problem is because SelectionEditorPrivate::setMouseCursor() sets the cursor shape to OpenHand via C++, but doesn't conditionally set it to ClosedHand. On the QML side in CaptureOverlay.qml, both are handled properly, but overridden by what the C++ code does. One should be removed, or else the other. Right now they're interfering with one another.
Hello everyone, I cannot reproduce this bug on my system, current OpenSuse Tumbleweed. KDE Plasma: 6.5.0 KDE Framework: 6.19.0 Graphics: Wayland Maybe this bug has been solved already and the report should be closed. Greetings
I cannot reproduce this bug on my system, Fedora 43.
What version of Qt are you folks who can't reproduce the bug using?
QMake version 3.1 Using Qt version 6.10.0 in /usr/lib64