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 is mainly about the previous progress dialogues.

Update Progress Bars

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:

Score layout, which is practically the whole time-frame for Save, Auto-Save, and Score Opening (and restoring a session). All that goes into a lower progress bar that's in the status bar down below. The Render MIDI will have a title-less pop-up during score-load. And finally, restoring session will show directly inside the pop-up splash screen on startup instead of something separate.

I sped these up because it takes longer than usual on this 200+ paged score:

1. Restoring Session + Shows Rendering MIDI which can and is skipped:

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

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

Aside, it makes me wonder how important it is to layout the score when saving. Can it be omitted to save time? My intuition says probably, but who knows. I may test it to see what happens. Either way, it's kind of neat to see when the score is autosaving. Sometimes if the user has a huge score loaded, it's awkward to not know why there's a seemingly arbitrary hangup during actions etc, and often times it's due to a timed autosave. I wouldn't not want to have these progress bars! Update: it doesn't layout except for saving the thumbnail, which apparently I already removed to save time earlier. For some reason I thought it was still doing a full layout, but it isn't. One thing I wouldn't mind doing here is have the progress bar when opening a score not from restore is to say "Loading Score" rather than "Layout" because again, it's the layout that's taking the 9/10ths of the load time.

List Selection

Oh yeah, one more thing. If a list selection occurs, and the types are all the same, 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

;)