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

We're past halfway through the official period!

So far

The last day I've beeen flying and having some issues with airport wifi so I apologize for the late blog pose (I'm home now though! :)). This week, I've been full speed ahead on voicing algorithms. I've got some kind of version of a few different algorithms and you can see them in action here:

And here is a look at the actual notes produced by a few of the algorithms

The past week was probably not so productive, since I have been busy with moving into my new college dorm… So no new features were added, and I mainly worked on bug fixes and code cleaning.

What I've done

• Code cleaning. The unused old plugin manager is completely removed. And most plugin related codes in resource manager also got moved into the new plugin manager. The resource manager now only handles displaying of plugins from repo, refreshing buttons' status, and

This week I've been working on adding an instrument change warning automatically when an instrument change is added. So far I have a very basic implementation that adds the warning when an instrument change object is added before some notes, and automatically moves the warning when more notes are added before the existing warning. The basic idea is that if an instrument change is added, it finds the next note on that staff (if there is one), and adds a

Works Planned To Do:

As mentioned in the last week's blog post, I wanted to set icons for the palette elements. To do this I had to understand how the icons for the elements were drawn, so most of the time I had to learn how the pre-existing code worked.

Work Done:

Completed setting the icons for the Palette Elements:

I started by creating a QPixmap by using a QPainter and also reimplemented the Palette::pixmap() function for making drawing the