More work todo before 2.0 … :-(
--
View this message in context:
http://dev-list.musescore.org/ottava-tick2-weirdness-tp7578621p7578657.html
Sent from the MuseScore Developer mailing list archive at Nabble.com.
--
Subv
Thank you for checking Leon. However this commit destroyed other things like
http://musescore.org/en/node/24905
http://musescore.org/en/node/24929
lasconic
2014-03-08 11:49 GMT+01:00 Leon Vinken :
> Just checked, ottava now behaves as expected, assume commit cff4e87b8f fixed
> this. It also solve
Just checked, ottava now behaves as expected, assume commit cff4e87b8f fixed
this. It also solves a number of MusicMXL import/export issue.
Thanks, Leon.
--
View this message in context:
http://dev-list.musescore.org/ottava-tick2-weirdness-tp7578621p7578652.html
Sent from the MuseScore Develop
I think you are right, tick2 is wrong. I will fix it.
On 25.02.2014 22:14, Leon Vinken wrote:
> In MuseScore 1.x, the tick2 value for an ottava was the end tick of the last
> affected note. Some time ago in the trunk this was changed to the start tick
> in of the last note. This leads to various fo
In MuseScore 1.x, the tick2 value for an ottava was the end tick of the last
affected note. Some time ago in the trunk this was changed to the start tick
in of the last note. This leads to various forms of weird behavior. E.g.,
when replacing the last note in an octave by two smaller notes, only th
