Use custom drag cursor that combines "cannot drop here" icon with arrow (for systems that don't do this by default)

• Mar 17, 2019 - 16:37
Reported version
3.0
Priority
P2 - Medium
Type
Functional
Frequency
Once
Severity
S5 - Suggestion
Reproducibility
Always
Status
active
Regression
Yes
Workaround
No
Project
MuseScore

OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.1.0.6041, revision: 5b23862

Drag-and-drop of symbols from palettes onto the score is no longer working.

Comments

• Mar 17, 2019 - 16:58
Status active ⇒ needs info

As usual, sample score and precise steps to reproduce the problem are needed. I cannot reproduce any sort of problem with drag & drop in current master.

Reply

• Mar 17, 2019 - 17:41
Title Workspaces: Drag and drop of palette symbols not working ⇒ Palettes; Drag and drop issue
Status needs info ⇒ open issues

OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.1.0.6052, revision: a9df4a0

The problem isn't actually as first thought. In MS2, when you drag, say, an articulation onto the score, there is a "+" sign next to the cursor, and the cursor is visible at all times. This allows the user to easily judge when to drop the symbol. However in MS 3.x there has been a change. A red prohibition symbol appears instead which not only gives the impression that the action is disallowed, but also hides the cursor until it is directly over the notehead. IME, this is making it more difficult to anticipate when to drop the symbol.

Reply

• Mar 17, 2019 - 18:34
Title Palettes; Drag and drop issue ⇒ Use custom drag cursor that combines "cannot drop here" icon with arrow (for systems that don't do this by default)
Severity S3 - Major ⇒ S5 - Suggestion
Priority ⇒ P2 - Medium

Actually, it was a bug and the source of much confusion for people in 2.x that we incorrectly showed the "+" even before the cursor was at a valid drop target. We received many complaints of the form "I dropped something onto my score but nothing happened", because people weren't aware they needed to drop to a specific location. This bug is fixed; we now obey the usual standard for drag&drop and show the "cannot drop here" cursor until you reach a valid drop zone and then the cursor changes to "+". However, it is unfortunate that the default "cannot drop here" cursor in Windows does not also provide an arrow to help with positioning. Blame Microsoft for this I guess; other OS's behave differently.

I will reclassify this as a suggestion that we ignore the system default cursor an instead provide our own that combines the "no" symbol with an arrow for easier positioning (this is actually the default on some systems, but not Windows 10).

See #278767: "no drop" mouse pointer badly positioned for more history and background.

Reply