Affected range not updated after key change

• Apr 5, 2018 - 17:36
Reported version
3.0
Type
Functional
Severity
S4 - Minor
Status
closed
Project

When adding a key signature, the score does not update to show how this affects subsequent notes and system headers. This bug is only in the master branch, and it does not occur when modifying an existing key signature.

To reproduce:

Start with a fresh "Untitled" score (formerly known as "My First Score").
Add a key signature to any measure in the first system.
Notice that the other systems do not show the new key signature.

This is simply a matter of Score::doLayoutRange() not receiving an appropriate value for etick, and thus not updating the entire affected range. I have written a patch to fix this, and am sending a pull request now.


Comments

This seems only to happen to My First Score and not to scores create from scratch or a template. And the reason seems to be that the former has system breaks. And sure enough, as soon as adding system breaks, other scores are affected too...