1.3. crashes in Mac Maverick when deleting measures with shortcut

• Feb 7, 2014 - 01:43

MacBookAir 11''
1,4 GHz Intel Core 2 Duo
2 GB 1067 MHz DDR3
OS X 10.9 (13A603)

I have re-created this, possibly bug.

In several score sheets of mine, the same effect: I highlight/mark an entire staff (e.g. left hand of a piano score), then press fn+ctrl+delete, and musescore crashes.

As far as I remember I have created this shortcut (fn+ctrl+delete) to delete a staff, or is this shortcut a default? Anyway, it seems faulty.

In a new empty score (2 staff piano notation), I do the same, here the entire system is deleted, when i press control+z (take back), it crashes.

I hope you can re-create this. I do not have problems with other shortcuts.
What to do?


Comments

I foyu do a search on "Mavericks" on this forum, you'll find this and a few other simialr issues already reported. Apparently Mavericks changed (broke?) something that causes crashes in MuseScore 1.3. Luckily, people on Mavericks seem to have good success downgrading MuseScore to 1.2.

In reply to by onigorom

Sadly the developers can do nothing apart from report the problem to Qt and Apple.

If neither ot them choose to do anything about it, then, sadly, 1.3 will remain unusable for Mavericks users.

For the record, the Mavericks upgrade has caused also caused problems with Sibelius.

In reply to by [DELETED] 5

It happens to me. Either Fn-Cmd-Del or Edit -> "Delete Selected Measures", but only in some files. I haven't found what feature of the file does this, yet. Mavericks 10.9.5, Mu 1.3/5702.

In this file (attached) multi-select measures 11-40 inclusive and try to delete them. Crashes every time, for me. Selecting only measure 11, you can delete it.

Delete the key signature in measure 31 and try it again (11-40). Now it works.

When it does work, it goes from 2 pages to 1 page due to deleting a measure (40) containing a page break. Something about that and the key signature in the same selection.

Attachment Size
scales5.mscz 6.83 KB

Do you still have an unanswered question? Please log in first to post your question.