In UX, back/cancel/etc buttons usually go on the left, while forward/confirm/etc go on the right. (Note that even the icon for "Back" is a leftwards-pointing arrow.) STK put the Back arrow button on general screens in the upper left corner, but before this commit, put back/cancel/etc on the right in dialogs and such. This commit fixes things to be in line with standard UX conventions, and also in line with the pre-existing upper-left corner Back button placement on screens in STK.
https://ux.stackexchange.com/a/63239
Since we only show one button at first, make it centered. (This is the continue button that switches from displaying race results to overall GP results.)
Fixes most of the occurrences of these warnings in the terminal/log:
[warn ] LayoutManager: Statically sized widgets took all the place!!
Removing these spacers did not make a difference in actual layout/spacing according to my testing.
`text_align="top"` isn't even valid, `top` is only valid for `text_valign`. Not sure how this got messed up in the first place, but this finally fixes it.
* Hide the cursor during gameplay
The cursor will show back up whenever:
- The mouse is moved
- The game is paused
- The race finished
This is probably not the best implementation, but it's a start.
* Wrap mouse display code in PT_MAIN checker
* Moved mouse display code to updateGraphics
* Protect SDL calls with #ifndef SERVER_ONLY
---------
Co-authored-by: Semphris <semphris@protonmail.com>
this fixes opaque shadow rendering on drivers that implement
mediump as 16bit
fixes#4855
Signed-off-by: Mike Blumenkrantz <michael.blumenkrantz@gmail.com>
Like other versions before, gcc 13 moved some includes around and as a
result <stdexcept> and <cstdio> are no longer transitively included.
Explicitly include them for std::runtime_error and snprintf.
