Creating new score doesn't switch active score Anatoly-os • Sep 11, 2018 - 12:08 Reported version 3.0 Type Functional Severity S3 - Major Status closed Project MuseScore Tags 3.0 If you create new score using e.g. templates, created score doesn't become active. Reply Comments Anatoly-os • Sep 11, 2018 - 12:10 Severity S4 - Minor ⇒ S3 - Major This is a regression introduced in one of the latest builds, so increased priority. Reply mattmcclinch • Sep 11, 2018 - 16:29 Status (old) active ⇒ patch (code needs review) Status active ⇒ Specifically, this is a result of https://github.com/musescore/MuseScore/pull/3915 to fix #275808: Crash in parts after undo-redo. Please see https://github.com/musescore/MuseScore/pull/3946 for a patch that fixes this issue, and a more correct fix for issue #275808. Reply Git Message • Sep 12, 2018 - 17:49 Status (old) patch (code needs review) ⇒ fixed Status ⇒ fixed Fixed in branch master, commit c5edc90fdf fix #276076: Creating new score doesn't switch active score Reply Git Message • Sep 12, 2018 - 17:49 Fixed in branch master, commit fe513082c9 Merge pull request #3946 from mattmcclinch/276076-tab-focus fix #276076: Creating new score doesn't switch active score Reply dmitrio95 • Sep 25, 2018 - 12:29 Status (old) fixed ⇒ patch (code needs review) Status fixed ⇒ Unfortunately the proposed patch still leads to an incorrect setting of an active score view when creating a new score. I made a new pull request (https://github.com/musescore/MuseScore/pull/3991) in order to fix it. Reply Git Message • Oct 4, 2018 - 13:48 Status (old) patch (code needs review) ⇒ fixed Status ⇒ fixed Fixed in branch master, commit 2e4ada5549 fix #276076, fix #275808: fix issues related to active tab tracking that led to crashes Also clarify the meaning of ScoreTab::setCurrent, setExcerpt, setCurrentIndex Reply Git Message • Oct 4, 2018 - 13:48 Fixed in branch master, commit 470e591679 Merge pull request #3991 from dmitrio95/fix-tab-close-crash fix #276076, fix #275808: fix issues related to active tab tracking that led to crashes Reply System Message • Oct 19, 2018 - 10:00 Status (old) fixed ⇒ closed Status fixed ⇒ closed Automatically closed -- issue fixed for 2 weeks with no activity. Reply
Anatoly-os • Sep 11, 2018 - 12:10 Severity S4 - Minor ⇒ S3 - Major This is a regression introduced in one of the latest builds, so increased priority. Reply
mattmcclinch • Sep 11, 2018 - 16:29 Status (old) active ⇒ patch (code needs review) Status active ⇒ Specifically, this is a result of https://github.com/musescore/MuseScore/pull/3915 to fix #275808: Crash in parts after undo-redo. Please see https://github.com/musescore/MuseScore/pull/3946 for a patch that fixes this issue, and a more correct fix for issue #275808. Reply
Git Message • Sep 12, 2018 - 17:49 Status (old) patch (code needs review) ⇒ fixed Status ⇒ fixed Fixed in branch master, commit c5edc90fdf fix #276076: Creating new score doesn't switch active score Reply
Git Message • Sep 12, 2018 - 17:49 Fixed in branch master, commit fe513082c9 Merge pull request #3946 from mattmcclinch/276076-tab-focus fix #276076: Creating new score doesn't switch active score Reply
dmitrio95 • Sep 25, 2018 - 12:29 Status (old) fixed ⇒ patch (code needs review) Status fixed ⇒ Unfortunately the proposed patch still leads to an incorrect setting of an active score view when creating a new score. I made a new pull request (https://github.com/musescore/MuseScore/pull/3991) in order to fix it. Reply
Git Message • Oct 4, 2018 - 13:48 Status (old) patch (code needs review) ⇒ fixed Status ⇒ fixed Fixed in branch master, commit 2e4ada5549 fix #276076, fix #275808: fix issues related to active tab tracking that led to crashes Also clarify the meaning of ScoreTab::setCurrent, setExcerpt, setCurrentIndex Reply
Git Message • Oct 4, 2018 - 13:48 Fixed in branch master, commit 470e591679 Merge pull request #3991 from dmitrio95/fix-tab-close-crash fix #276076, fix #275808: fix issues related to active tab tracking that led to crashes Reply
System Message • Oct 19, 2018 - 10:00 Status (old) fixed ⇒ closed Status fixed ⇒ closed Automatically closed -- issue fixed for 2 weeks with no activity. Reply
Comments
This is a regression introduced in one of the latest builds, so increased priority.
Specifically, this is a result of https://github.com/musescore/MuseScore/pull/3915 to fix #275808: Crash in parts after undo-redo. Please see https://github.com/musescore/MuseScore/pull/3946 for a patch that fixes this issue, and a more correct fix for issue #275808.
Fixed in branch master, commit c5edc90fdf
fix #276076: Creating new score doesn't switch active score
Fixed in branch master, commit fe513082c9
Merge pull request #3946 from mattmcclinch/276076-tab-focus
fix #276076: Creating new score doesn't switch active score
Unfortunately the proposed patch still leads to an incorrect setting of an active score view when creating a new score. I made a new pull request (https://github.com/musescore/MuseScore/pull/3991) in order to fix it.
Fixed in branch master, commit 2e4ada5549
fix #276076, fix #275808: fix issues related to active tab tracking that led to crashes
Also clarify the meaning of ScoreTab::setCurrent, setExcerpt, setCurrentIndex
Fixed in branch master, commit 470e591679
Merge pull request #3991 from dmitrio95/fix-tab-close-crash
fix #276076, fix #275808: fix issues related to active tab tracking that led to crashes
Automatically closed -- issue fixed for 2 weeks with no activity.