| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
This will be the first half of properly handling on screen dirty rects.
|
|
This reverts commit f69dfba21a5d4be8cc60a20a0dd0628717fa5373.
|
|
This should help improve performance when scalers are being used.
|
|
|
|
|
|
|
|
|
|
|
|
2 as well
|
|
|
|
|
|
|
|
|
|
Thanks LordHoto for reminding this
|
|
|
|
|
|
|
|
|
|
in-game scene
|
|
This matches the casing of the original engine name.
|
|
implementation of Scene 100 (Title Screen)
|
|
appropriate
|
|
|
|
|
|
This tries to make our code a bit more compliant with our code formatting
conventions. For future use, this is the command I used:
git ls-files "*.cpp" "*.h" | xargs sed -i -e 's/[ \t]*$//'
|
|
Conflicts:
engines/tsage/ringworld_scenes1.cpp
engines/tsage/ringworld_scenes5.cpp
engines/tsage/tsage.h
|
|
|
|
This should correctly handle re-enabling the cursor when restoring savegames.
|
|
|
|
|
|
This also fixes the problem with the cursor appearing in cutscenes when you press any key
|
|
|
|
|
|
|
|
|
|
This fixes Valgrind warnings when getEvent() is called when there are
no pending events at all.
|
|
|
|
|
|
|
|
I'm still not completely happy with how it's implemented, and the original code is very obtuse when it comes to cursor display; it will likely need further investigation later on so the cursor doesn't appear in cut-scene scenes
|
|
|
