Mandolin tab mute string
Possible bug. Referring to screenshot:
In note input mode, on top string.
shift+x results in second string with an x, not top string
Other strings work correctly.
$ uname -r
5.4.0-42-lowlatency
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Codename: focal
MuseScore 3.5.0 fbc202
Comments
I see what you mean. I ignore how it's supposed to work internally, but as far as I know, the Shift + X shortcut is not intended to work in Tablature input mode in the first place.
If you enter a fret number first, and then apply the shortcut, then everything works as expected as far as I can see (or, in normal mode, by selecting the whole chord or chords, and then applying the shortcut).
In reply to I see what you mean. I… by cadiz1
If the Shift-X shortcut is not intended to work in Tablature, then it should not work at all.
As it is, it behaves erratically by the behavior I stated and other similar ways. In general the behavior is recreated by having any string with a fret number, the move to another string (indicate by the light blue rectangle) and enter Shift+X .
In reply to If the Shift-X shortcut is… by allelopath
Apparently you didn't understand me. I'll try to do otherwise. Look at the following GIF: in input mode, if I move the cursor from one string to another, and directly type the shortcut Shift + X at each string change, nothing happens, right? And this is the behavior as expected.
On the other hand, if you first enter a fret number and then apply the shortcut, it works as expected. To sum up, don't forget to enter a number first before the shortcut, and don't wait until a simple string change on the TAB, just using the shortcut might be enough.
In reply to Apparently you didn't… by cadiz1
In fact, what you have done is this (just before getting the cross on the 2nd string/and the result of your image in first comment)
You have entered fret 2/B note, then move the cursor over the first string, and finally apply the shortcut. But it is the note that is selected (the 2 highlighted in blue - picture below), so the shortcut applies to that note, and not because you move the cursor on another string/top string here.
In reply to Apparently you didn't… by cadiz1
I did understand you and thanks for the gif for completeness. I understand that user must enter a fret number and then enter Shift-X. That is the problem, that the user must first enter a fret number, otherwise erratic behavior results. When a line is highlighted blue with no fret number entered, the Shift-X is entered it affects another line. This cannot possibly be seen as expected behavior. So when a line is highlighted blue with no fret number entered, one of two things should happen:
1. The x is added to the line
2. Nothing
1 is preferable.
2 is acceptable.
In reply to I did understand you and… by allelopath
"That is the problem, that the user must first enter a fret number, otherwise erratic behavior results. When a line is highlighted blue with no fret number entered, the Shift-X is entered it affects another line"
It is not a erratic behavior. The Shift-X doesn't affect another line: it affects the selected/highlighted note-fret (and not necessarily where is the cursor) . It's something to learn :)
In reply to "That is the problem, that… by cadiz1
We're going to have to agree to disagree here.
Thanks for your time, I do appreciate it!