Promote use of internal progress bars #2411
Merged
+100
−53
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The internal progress bars weren't displaying at all due to recent changes in the graphics stack (#1766). The progress bars use
Gfx::renderAndUpdate
to refresh the screen, but after this refactor, onlySoftwareDrawingEngine::render
was being called, but theSoftwareDrawingEngine::present
it introduced was not. This left the screen un-updated.In addition to this, I reshuffled the main
OpenLoco::initialise
function to prioritise G1 loading and GUI init, such that we now have internal progress bars for the object and scenario indexing processes. Getting to G1 init happens so quickly, I believe we can just do away with the remaining Win32 ones.