This week I've been working on finishing and stabilising the instrument change warning system. I started off the week by fixing the undo/redo functionality for all the different aspects of the system, such as deleting an instrument change, deleting a warning, and deleting the note underneath a warning. After this, I started work on making sure that files with instrument changes saved correctly. After talking about this in the developers chat, we decided that the best way to do this

Work Planned To Do:

Last week I was trying to implement the drag and drop and the mouse double-clicked function to use the elements in the palette. As mentioned in the previous blog I had to start from scratch by using the PaletteCellItem (QListWidgetitem) instead of the PaletteCells.

Work Done:

Completed implementing the double-clicked functionality for the palette Element. This enables the user to apply the element to the score by double-clicking the palette element. This time I started by

This week's work involves a lot of bug fixing, refining and code cleaning. Some notable work includes:

1. I made DownloadUtils cancellable by adding a slot function cancel() that can abort the download process. This is useful when for example, we're closing Resource Manager and the threads that are loading metadata haven't finished, especially when the Internet is slow and we don't want that thread to keep occupied in the thread pool.
   Here it's important to distinguish threads for different purposes

In the final quarter!

So Far

This week has been a bit of an interesting week for me. I spent the first half of the week working on the stuff mentioned in last weeks blog before having to scrap all of it (for now at least) in favor of getting this project ready to be merged (so that everyone can use it sooner :)). I spent a couple days looking at TODOs and FIXMEs that I left behind and resolved

I spent the first half of this week converting the instrument change warning text, which was previously a staff text object, to a new custom class. This has allowed me to do things like change the style of the object (it now matches instrument changes), and add the correct behaviour for deleting notes under the warning, allowing the text to move properly automatically. Adding the new object proved quite difficult, as there are a lot of places in the code

Work Planned To Do:

Last week I was mainly trying to reimplement the drag and drop and the mouse double-clicked function to use the elements in the palette. To do these, I started reimplementing each of the function provided in the old palette to make it more relevant to the ListWidget of the new palette.

Work Done:

I couldn’t do much work last week since I had a fever for over 3 days and was recovering from that this Monday,

Hi!

I have smoothly finished what I planned to do last week:

1. Background fetching metadata about plugins, extensions and languages. The resource manager launches much faster now, and the user is now able to operate on installed plugins no matter whether the plugin store, languages or extensions finish loading.
   [inline:loading2.gif]

2. Displaying plugin package descriptions. The descriptions are fetched from each plugin's detail page. And only the specific HTML div section is fetched.
   [inline:description.gif]

Besides, I had to deal with several

We're actually about 2/3 through now :) I was wrong last week

So far

Last week I worked mainly on testing, improving existing voicings, and the automatic extension system. For testing I realized that there were a lot of cases not being covered by the tests. In fact I modified one of the voicing algorithms and the corresponding test still passed since the issues I fixed were never even covered by the tests in the first place. Now the tests

This past week I have been working on fixing the issues of the instrument change warning text. I first managed to fix the broken tests, which was a problem with how some of the methods I had written worked with linked scores. I then started working on changing the existing implementation of the text, which simply created a new staff text object, to a custom type called InstrumentChangeWarning. This has the advantage of allowing me to implement custom behaviour for

Work Planned To Do:

In the blog that I posted last week, I mentioned that I will be implementing the Palette navigation using the arrow keys. As promised, I was also able to complete the keyboard navigation feature. This took more time than I expected since I faced some technical difficulties.

Work Done:

Completed Palette Navigation

I started by reimplementing the keyPressEvent() inside the Palette List. The new keyboard navigation allows one to go through the grid of elements uniformly