[trunk] Changing duration beyond measure limit causes crash [DELETED] 5 • Nov 25, 2010 - 08:39 Type Functional Severity S2 - Critical Status closed Project MuseScore r3727 Create a flute score Add 4 quarters in the first measure Exit note entry Select the last quarter by clicking in the notehead Press 6 or choose a half note in the toolbar -->Crash Reply Comments David Bolton • May 1, 2011 - 17:37 Apparently fixed? Not able to reproduce using r. 4245 nightly build, Windows 7 Reply chen lung • May 1, 2011 - 23:28 The log indicates this was fixed (28 April), but it may apply to all voices, rather than just one. #8996: Not possible to change a value beyond bar in multi-voice I can't reproduce using MuseScore 2.0 nightly build (4245) - Windows XP SP3. I'm using an earlier nightly build on Mac (4233), where it is present (I'm sure it won't be in the upcoming one). Reply System Message • May 15, 2011 - 23:30 Status (old) fixed ⇒ closed Automatically closed -- issue fixed for 2 weeks with no activity. Reply
David Bolton • May 1, 2011 - 17:37 Apparently fixed? Not able to reproduce using r. 4245 nightly build, Windows 7 Reply
chen lung • May 1, 2011 - 23:28 The log indicates this was fixed (28 April), but it may apply to all voices, rather than just one. #8996: Not possible to change a value beyond bar in multi-voice I can't reproduce using MuseScore 2.0 nightly build (4245) - Windows XP SP3. I'm using an earlier nightly build on Mac (4233), where it is present (I'm sure it won't be in the upcoming one). Reply
System Message • May 15, 2011 - 23:30 Status (old) fixed ⇒ closed Automatically closed -- issue fixed for 2 weeks with no activity. Reply
Comments
Apparently fixed?
Not able to reproduce using r. 4245 nightly build, Windows 7
The log indicates this was fixed (28 April), but it may apply to all voices, rather than just one. #8996: Not possible to change a value beyond bar in multi-voice
I can't reproduce using MuseScore 2.0 nightly build (4245) - Windows XP SP3. I'm using an earlier nightly build on Mac (4233), where it is present (I'm sure it won't be in the upcoming one).
Automatically closed -- issue fixed for 2 weeks with no activity.