Community Blog

This final post will sum up all of the additions and changes I have made to MuseScore for 2022’s Google Summer of Code harp pedalling project.
The previous blog posts with weekly updates can be found here.

As the team are working towards the release of MuseScore 4.0, this code will only be merged after its release and be included in a 4.x update.

Code changes

• Pull requests submitted as part of this project

PR #12269 contains feedback

Hi,
As we're getting to the end of GSoC, I spent this week tidying up and making changes based on code reviews. The largest change I made was how pedal diagrams were accessed in the score by the proofreading function and other diagrams - eg. for updating the text of a diagram further ahead in the score based on a change earlier. This was previously done by looping through all elements of a score until a diagram is found. This

Shortcut Categories

Since a few concerns were reported in PR #12752, this week's focus turned toward that PR.

• There was a problem with the clumsy opening/closing animation in which the text remained for longer than it should have. I resolved this by implementing (but not yet pushing) a change in opacity when the section closes, which should make it seem better.

• The section title's font was also not bold; this has been corrected.

• There are also some refactoring concerns, such

Hi all,

This has been a productive week of fixing bugs, tests and layout issues. With everything up to date, I'm ready for a code review and some final pointers as to placement and layout. These will only be small tweaks without huge amounts of refactoring (I hope) so am on track for the final deadline at the beginning of September.

I also spent some time implementing a proofreading feature for the diagrams. This updates the colour of the noteheads

Palette Shortcuts

This week was devoted exclusively to enhancing and improving the code for palette shortcuts. For instance, there was a location where palette cells were being stored unnecessarily. It effectively served as an intermediary. I eliminated this intermediary and directly iterated over the palette cells to produce action names. In the following weeks, I will continue to work on optimizing this and making the code as clear as possible, since I feel that certain portions of the code are

Hi,

This week has been productive in getting my branch rebased and fixing some layout problems. There are still some edge cases to work out, but the UI is looking much better. I've also included some missing functionality linking all diagrams in a score. When one diagram is edited, the score is searched for text settings further ahead. If they need to change, the diagram text is "calculated" again and updated.

My final tasks for the diagram are tidying up

Palette Shortcuts

After tidying up and fixing a few issues with palette shortcuts. The proof-of-concept PR version is now complete and available: #12850

The system flow is straightforward. You may assign a keyboard shortcut to a palette item from either the palettes by right-clicking and left-clicking the desired menu item (add/delete) or the preferences page. Although the name on the preferences page is quite cumbersome and only for development reasons.

[inline:MuseScore4_JgU1TcXikU.png]

Shortcut Categorization

[inline:CategoriesShortcuts.png]
The shortcuts classification PR draft is also complete

Hi,

This week was spent tidying up the last bits relevent to the MVP. Unfortunately, the placement of the diagram on the score is proving difficult and isn't quite finished yet.
I talked to a few harp players, looked through some music and had a go on a pedal harp (which was quite difficult - not an option for a career change!) to give me a feel for where pedal changes should be placed "horizonally" on a score. Damping of

Palette Shortcuts

In the eighth week, significant progress was made on palette shortcuts. However, after consulting with the team, it was determined that this feature must remain a proof-of-concept for the time being. The justification for this is that there are a number of issues that directly impact this.

• For instance, activities using default keyboard shortcuts cannot be cleared.
• If new palette components are introduced in an update, the user cannot simply add them without resetting his palette settings, which

Hello everyone,

As we've reached the halfway point in the project, I have completed my MVP. The final pull request can be seen here There are a few issues left to sort out, mainly concerning the behaviour of the pop-up when opened. However, the UI and score elements I implemented earlier have married up very nicely, hopefully offering an easy and intuitive way of editing them.
Here's an example of a user adding a diagram.
[inline:Pedal diagram demo.gif]
Ex 1: