Parentheses around accidentals do not carry over between score and part or vice-versa

Issue type

Engraving bug (incorrect score rendering)

Description with steps to reproduce

1. Open a score that contains parts. Then open at least one part.
2. Add notes with accidentals to either the score or the part; then place some or all of the accidentals in parentheses. Save the score, then examine the part or the score, whichever is not edited directly. The accidentals do not carry over.

In this case, I removed parentheses in the score, which did not carry over to the Alto part, where I had originally added these.

Supporting files, videos and screenshots

In which versions of MuseScore Studio is this issue present?

MS 4.7.4

Regression

I was unable to check

Operating system

macOS 15.7.7

Additional context

In Renaissance polyphony, it is sometimes easier, whether creating a new edition from a part-book or transcribing/correcting existing editions from a printed source of some kind, to open the voice parts and edit each individually. (This is what I prefer anyway.)

This means that I place accidentals in parentheses or brackets, either as confirmation that the accidental earlier in the measure continues (because this music, lacking our does not have the rule that the sign is valid until cancelled explicitly via a bar line or another sign) or to clarify cross-relations or ambiguity over whether a note should be altered: I prefer brackets for editorial decisions and parentheses for clarifying that a note should be altered when repeated, if the sign is not present in the original, in which case I use a normal staff accidental).

I suppose this is also a thorny issue: there's no option here to synchronize (which I would expect): it's possible that you don't want or need the parentheses in the part but would in the score, but I'd also expect synchronization to be a default that can be toggled off.

Checklist

• This report follows the guidelines for reporting bugs and issues
• I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
• I have attached all requested files and information to this report
• I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible