Customise time signature appearance (using cut/common time symbol) directly in "Add custom time signature" dialog
#25,704 建立於 2024年12月3日
倉庫指標
- Star
- (11,122 star)
- PR 合併指標
- (平均合併 9天 4小時) (30 天內合併 153 個 PR)
描述
Issue type
UI bug (incorrect info or interface appearance)
Description with steps to reproduce
Many renaissance works alternate between some kind of 2/1 and 3/1 meter, usually written with cut time 𝄵 or common time 𝄴 symbols and a single digit 3 or 3/2 time signature. Therefore it would be nice to be able to make a user-defined 2/1 or 4/2 time signature that shows as cut/common time. However this is currently not possible.
Steps to reproduce:
- Go to time signature palette and see that the existing pre-defined time signatures don’t include what you want. → No problem.
- Add custom time signature 4/2 to palette. → See that you could change the displayed time signature to another fraction or a single digit but not to cut/common time symbol.
- Apply the custom time signature to score.
- Change the displayed time signature via context menu. → See that you can change the displayed time signature to cut/common time or another special symbol but is changed only on one staff.
Supporting files, videos and screenshots
https://github.com/user-attachments/assets/2a4440ac-5abf-43e4-adb0-c3a6da8982cd
What is the latest version of MuseScore Studio where this issue is present?
4.4.3
Regression
I was unable to check
Operating system
Linux but it should be OS-independent
Additional context
IIUC step 4 shows an example of bug #16406. Step 2 might be related to #12980 but I think the renaissance scenario is a special case that could be easily treated by adding the possibility of display cut/common time to the “create time signature” dialog.
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