heads up - incoming issues, overall impressions

This is mostly a heads up that I just tried using 2.0 full on for a project a couple of days, and I'll be submitting a bunch of issues - as many as I can make into reproducible cases.

But I figured this would also be a good opportunity to put in a word about my overall impressions.

First, I really like how 2.0 looks and feels. When I ultimately had to return to 1.2 after determining 2.0 just wasn't up to the task yet, it really felt like a regressing into a less polished interface in most ways. I understand there may be redesign yet to come and I'm certainly open to further improvement, but I do really consider the current 2.0 interface rather nice.

On the other hand, there were a small number areas where it felt like 2.0 was a step backwards (aside from the outright bugs) in usability, though, so a couple of the issues I submit will reflect this. There are also some issues with new features that I think will limit their usefulness.

There are some long-standing bugs / limitations that I think really need to be addressed for 2.0. I intend to bump these, resubmit, or perhaps log them for the first time, as appropriate. But to summarize, the single biggest overall set of issues I run into regularly has to do with interactions between barlines, system breaks, and/or multimeasure rests. There are just too many where it is impossible to get things to come out as one wants, or where things are silently done incorrectly when generating parts. Things like #12918: Double bar + key sig change + break + delete break removes the double bar and #9390: clef change not displayed after multimeasure rest. I'm a little bit afraid it will turn out there are some architectural reasons why fixing these may not be easy, but hopefully I'm wrong about that.