Update progress bars for layout/save/render midi + other fixes

[worldwideweary]

Haven't been really sticking with the idea of single concepts for Pull Requests, but it is what it is. This will probably this kind of large PR, and it's mainly about the previous progress dialogues, but then it became another big collection of changes in the process of having to update things.

Update Progress Bars

• Score loading, saving, layout, and also MIDI rendering will have progress bars in the status bar. No pop-ups for rendering midi like shown in the video below (outdated). Score loading and MIDI rendering will allow user to press ESC to prematurely quit the process, both within the main program and during Restore Session with the splash screen: during loading phase, if the user presses ESC, it will cancel loading the score and not open a tab for it.

• Continuous View is one system. It's different than Single Page, and I can't calculate a smooth percentage because it occurs in different "sporadic" phases of layout rather than an accumulation of pages, but I've found a compromise at least to give some sort of percentage (here's a large score loading, choppily compared to the smoothness of page/single page view):

continuous.mp4

• Splash Screen retained when clicking on it or if changing window focus. This is in order to allow user to press escape if needing to cancel the Restore Session phase. Originally, it would just hide as default QSplashScreen behavior.

After getting #210 working, I had the unfortunate occurrence of auto-save pop-up while looking through style settings or something, and then when the pop-up was done, focus went back to the main app rather than the preference settings dialog. And layout occurs after changes, so it was constantly losing focus. This motivated me to get something more subtle, so I decided to go with using a QProgressBar shown in the Status Bar located at the bottom of the screen. Problem there is that there's one instance of needing to be able to cancel during the progression: Rendering MIDI on during load of score or restoring previous session if the property is enabled to allow pre-loading the midi.

Instead of having all these progress options to show or not, this is what'll happen: There's only one option, and that's loading MIDI events on loading a score. Everything else will be automatic:

Outdated:

1. Restoring Session + Shows Rendering MIDI which can and is skipped: (pop-up is out of date)

splash2.mp4

Saving shown on status bar:

saveStatusBar.mp4

Automatic Curly Quotes

For now, in order to get regular vertical slabs, user will have to use CTRL+' or CTRL+". There's no undo-stack like with 4.x version to get the vertical ones. Curly comes automatically:

Beginning Text Editing will update the view to try to include the system's entire top and bottom skyline.

Fixes

Things that should've been in the first place

Splash Screen

Looks different than usual with a blue-grey gradient and a cute sub-version: 3.7.1

It's nice to see when the score is autosaving. If the user has a huge score loaded, it's awkward to not know why there's a seemingly arbitrary hangup, and often times it's due to timed autosaves. I wouldn't not want to have these progress bars!

List Selection

With a list-selection of all same types, information regarding the first element of the list will display. So like a key signature on a grandstaff for instance will show the information instead of merely "List Selection". Mouse hovering worked anyway for this stuff on this version, so whatever, but still. And if the types are different, the statement says so:

Oh boy:

And if hovering over an item, there now is a text saying "Hovering over" to re-affirm that's what it is instead of a selection

• Note-entry now has a distinct look which I'm not necessarily all in about, but for now... If I remember, it might be slightly taller, but is aligned to the left as a "pre-cursor" instead of highlighter (The color's a little funny in my 3.6.2 right now)

instead of 3.6.2:

Efficiency: Speed up text editing. 3.6.2 originally does a full layout for each keystroke of the musical system surrounding it, which can be slow on a large score if you type fairly quickly. I'm one of those people who absolutely hate the feeling of "slow down" when doing something like typing. I've ripped that out and the final layout gets registered when exiting edit mode. Way snappier, but at the cost of maybe having the y-offset slightly off during edit until finalizing edit, which is fine by me.

Experiment:

• Set ui/score/elements/override/color/inactiveMeasure to have a distinct color override for every element not found within the current measure (note entry cursor or playback cursor).
• Either 1) keep it black + changed alpha to honor the elements' distinct colors but override their alpha transparency, or 2) change the color entirely for everything. Kind of a gimmick, but whatever:

Float Mode

• There's a hidden mode called "Float" that is a page view but doesn't vertically space the systems. It's like a "Minimal spacing" Vertically continuous page, like Single Page, but again without extra spacing and omits the line breaks/page breaks. It's impractical