MuseScore

musescore:3.5.2

  1. Git
  2. lp:musescore
  3. 3.5.2
Last commit made on 2020-10-16
Get this branch:
git clone -b 3.5.2 https://git.launchpad.net/musescore

Branch merges

Branch information

Name:
3.5.2
Repository:
lp:musescore

Recent commits

465e7b6... by pereverzev_v <email address hidden>

Set up proper version number and fixed set build config

257872d... by Igor Korsukov <email address hidden>

disabled palette test

a470fc3... by Niek van den Berg <email address hidden>

Revert "Fix #257581, Fix #64636 - Changes to Measure properties are not propagated between score and existing linked parts after save/reload"

This reverts commit 2c7435b19e4b774070985acfc8c25d8b356d30d3.

105e11a... by Igor Korsukov <email address hidden>

added error handling on CI

d0afb5a... by Igor Korsukov <email address hidden>

added index.html for ftp, setup schedule

874413a... by Igor Korsukov <email address hidden>

added nightly builds

3c3a8af... by Joachim Schmitz <email address hidden>

Fix issue with en_US translation getting fed back into Transifex

simplify CMAkeListe.txt for tours and save some space by not
installing any *_en.qm files

f3d3871... by Marc Sabatella

update tests

c7d3364... by Marc Sabatella

fix #311520: harmony playback preferences not honored until toggled

Resolves: https://musescore.org/en/node/311520

The new preferences for disabling playback of chord symbols work fine,
only ater you've toggled them at least once, which forces them
to be written to the ".ini" file.
Otherwise, they are not being initialized correctly.
This is apparently from the use of QSettings to access the preferences
from code within the libmscore folder.
This technique is used at least one other place,
but it is apparently not reliable with respect to default values.

This commit adds new members of MScore class
so mscore can write them and libmscore can read them.
That is the approach used by most other preferences
that need to be accessed from libmscore.

In addition, there was a logic error
when creating a new score from a template.
There was code to handle new scores created from *old* templates,
so they wouldn't have chord symbols forced off
by the compatibility setting.
This code was erroneously being triggered for new templates as well,
making it impossible to disable chord symbol playback via a template.
That is fixed by performing the same version check used
when reading the template.

9d5d395... by Igor Korsukov <email address hidden>

fix #311621: fixed export audio on Windows