Nightly- Bug. lettres Tab française

J'ai trouvé la solution! De contournement, peut-être, mais elle me satisfait complètement. Elle me comble, même, dirais-je!
Pour être honnête, c'est Miwarre, sur le forum anglais, qui me l'a fourni. Grand merci à lui :-)

En effet, la touche clavier H entre en conflit avec le raccourci du crescendo. Et le I avec celui du choix des Instruments (on peut toutefois, dans ce cas, contourner le problème en choisissant le J... qui devient I sur la tab en lettres). Ensuite, cela se complique encore davantage car il n'y a pas de touches programmées par défaut pour les cases supérieures à 10.

Le plus simple (de très loin) et le plus efficace (complètement efficace, j'en souris encore, tellement surprise et découverte ont été totales et époustouflantes!) est de faire le choix, d'emblée, de saisir des chiffres.

Ensuite, seulement, si l'on préfère les tabs en lettres (et quelque soit le type de police), vous allez (vous retournez, plutôt) dans "Style" -> Staffs Type -> Full Configuration > Frets marks -> switcher l'onglet numbers par celui de letters, et vous obtenez le résultat suivant (voir les trois fichiers attachés) :-)

Avant cela, et pour les anglophones, je fournis, ci-après, la réponse in extenso de Miwarre.

------------------------------------------------------------------------------------

Posted by Miwarre on April 6, 2014 - 8:48am

*) H: The issue with 'h' is indeed a shortcut conflict with another function (crescendo, in this case) being assigned the same keystroke in the default setup. Possible solutions:

the user who regularly needs French tablatures redefines the Crescendo shortcut to something else (but should be informed in some way of the need to do so);
a different shortcut for Crescendo is provided as a default
the Crescendo shortcut is limited to non-tablature edit mode

*) I/J: The default letter shortcut for the 8th fret is [J], as [I] is already used by default setup for [I]nstrument (as it can be discovered by looking at the "Edit | Preferences | Shortcuts" dlg box).

*) M-...: Shortcut for frets greater than 9 are not even defined. Possible solution:

Shortcuts for frets greater than 9 (10 - 13?) are defined in the code, but not assigned any key by default; the user needing this feature may assign the key(s) he prefer (and manually resolve the conflicts which would arise almost inevitably).

However, I cannot confirm that a wrong letter is entered by using one of those key strokes; rather, nothing is entered as the shortcut is simply reject by the framework.
____________________

As a (temporary?) work-around, note that both number and letter shortcuts are always active during tablature entry, as they refer to the fret value regardless of how this value is displayed. So, the 10th fret can always be entered with [1] + [0] (and so on for higher frets) and will be correctly displayed with digits or letter according to the staff setup.
____________________

In general, shortcuts for tablatures have always been a source of problems and, as far as I know, no definitive solution has been found and proposed.

The number of needed shortcuts is relatively high (about two dozens for the fret values only, plus other to move around in the tab, to select/change the note duration value, to increase/decrease the pitch or string of a note, etc.) and many obvious choices for these actions are already assigned to general programme functions.

Currently, a partial solution is implemented which 'filters' shortcuts according to the programme mode; for instance, shortcuts to enter notes based on pitch ("A", "B", ...) or on interval ("Add a second above", "Add a third above", ...) are disabled in tab. entry mode, as they have little use in tabs. Some of them have been disabled just because their default keystroke happens to be 'needed' for tablatures (like "enharmonic up", to 'free' the [J] key). In addition, this requires special code and setting juggling at each change of programme state, as Qt shortcut machinery has no notion of "state" (see https://github.com/musescore/MuseScore/blob/master/mscore/musescore.cpp…).

This is rather clearly sub-optimal, but I've run out of solutions and I still hope someone will come up with a genial breakthrough. Anybody volunteers?

Thanks,

M.