No status bar in nightly build geetar • Nov 4, 2015 - 15:52 Type Functional Severity S4 - Minor Status closed Project MuseScore Nightly d45cc19 / Win 7. There's no status bar visible in this nightly. It was there in MS 2.0.2. Reply Comments Shoichi • Nov 4, 2015 - 15:57 74281d4 seems ok Reply Jojo-Schmitz • Nov 4, 2015 - 16:07 Status (old) active ⇒ needs info are you sure you just have switched it off by accident? Check whether Status bar is checked in the View menu Reply geetar • Nov 4, 2015 - 16:17 Yes the status bar was ticked in the view menu but still not visible. Unticking it in the view menu and then reticking fixed the problem. Reply Marc Sabatella • Nov 4, 2015 - 16:22 If you find a way to reproduce this condition reliably, please post the steps here. For now though, probably nothing to be done about it. Reply Jojo-Schmitz • Nov 4, 2015 - 16:24 Status (old) needs info ⇒ closed Might have been some incomatibility in the preferences Settings bewteen the cuttent and last build you used? Anyway, reopen if you can reproduce Reply
Jojo-Schmitz • Nov 4, 2015 - 16:07 Status (old) active ⇒ needs info are you sure you just have switched it off by accident? Check whether Status bar is checked in the View menu Reply
geetar • Nov 4, 2015 - 16:17 Yes the status bar was ticked in the view menu but still not visible. Unticking it in the view menu and then reticking fixed the problem. Reply
Marc Sabatella • Nov 4, 2015 - 16:22 If you find a way to reproduce this condition reliably, please post the steps here. For now though, probably nothing to be done about it. Reply
Jojo-Schmitz • Nov 4, 2015 - 16:24 Status (old) needs info ⇒ closed Might have been some incomatibility in the preferences Settings bewteen the cuttent and last build you used? Anyway, reopen if you can reproduce Reply
Comments
74281d4 seems ok
are you sure you just have switched it off by accident? Check whether Status bar is checked in the View menu
Yes the status bar was ticked in the view menu but still not visible. Unticking it in the view menu and then reticking fixed the problem.
If you find a way to reproduce this condition reliably, please post the steps here. For now though, probably nothing to be done about it.
Might have been some incomatibility in the preferences Settings bewteen the cuttent and last build you used? Anyway, reopen if you can reproduce