keyboard shortcut 5 doesn't work for quarter duration on AZERTY keyboard

regression vs. which version?
What do you mean by 5/(, (and by 2/é, 3/", 4/', 6/-)?
And what by black?

OK, so 5 should sets a quarter duration, and does for me and, as far as I can tell, for anyone else, just like 4 sets an 8th and 6 sets a half, are you saying that 2,3,4 and 6 work to set their durations but 5 does not?

I can confirm.

I think this is caused because '(' has been set as the default shortcut for parenthesis somewhere along the 3.x chain; which conflicts here for Azerty users

Sure enough, after clearing the shortcut for adding parenthesis the duration shortcut works again.

Guess that's a a case for the (first time) startup wizzard and the shortcuts_AZERTY.xml file then?

it has

  <SC>
    <key>interval5</key>
    <seq>Alt+5</seq>
    <seq>Alt+(</seq> <!-- AZERTY for 5 -->
    </SC>
 

(more than once) and

  <SC>
    <key>add-parentheses</key>
    <seq>(</seq>
    </SC>
 

I guess the latter is what's causing this issue?

So it is "broken" since 3.1 https://github.com/musescore/MuseScore/commit/015e73652bd84165f665562bd…

My immediate reflex would be to remove the default shortcut for add-parenthesis as I use that way less than changing durations; or set that one to the closing ')' instead (which is still available). The current definition makes the conflict so that neither action works out anyway.

fix should be in shortcuts_AZERTY.xml indeed

Strange that it took so long to get detected?

It is curious, or not completely clear here.
The 5 (to choose the duration of a quarter note) on the numeric keypad works perfectly here, with an AZERTY keyboard. And I don't remember any report of failure on this subject in the past ?
However, when it comes to Tablature (the 5 of the alphanumeric part of the keyboard/the row of numbers above the letters), this is an issue that has been reported and known for a long time, see: #292716: [TAB] Conflict between fret/number 5 and shortcut "Add parentheses to element" (AZERTY)
So either it's directly related (depending on the user's choice of shortcuts, or type of keyboard - with numeric keypad or not, I don't know), or it's a duplicate (rather!)

• I temporarily mark it as "Needs info" for clarification about these points.

It is a duplicate, it is not about the numeric keypad

See https://github.com/musescore/MuseScore/pull/7887 and https://github.com/musescore/MuseScore/pull/7888

Both pull requests have been merged.

Automatically closed -- issue fixed for 2 weeks with no activity.

Hi,

This is still broken in Musescore 4.1 I'm using Macos with french azerty layout.
I haven't tried the workaround yet.

Then it is a new/different issue. Check GitHub whether it is reported there, this issue tracker here has been discontinued