| Age | Commit message (Collapse) | Author |
|---|
|
All these fall through were marked as deliberate, so again I've only
changed the comment to silence GCC.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
scene 9500
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Also:
- some minor refactoring in scene 30
- bugfixing of background in scene 50
- modification of original behavior for LOOK cursor on the wall, which was inappropriate.
- misc comments of useless objects
- reduce scope of some variables
|
|
|
|
variable
|
|
|
|
|
|
|
|
preserved.
|
|
|
|
source file
|
|
This would happen in Ringworld when clicking on the slot in the
flycycle. I have compared the behaviour to the original, and I
can't see any obvious differences after my change. CID 1003728
|
|
|
|
Powered by:
git ls-files "*.cpp" "*.h" "*.m" "*.mm" | xargs sed -i -e 's/[ \t]*$//'
|
|
|
|
reporting it.
|
|
This will be the first half of properly handling on screen dirty rects.
|
|
This reverts commit f69dfba21a5d4be8cc60a20a0dd0628717fa5373.
|
|
This puts them all in the common SceneHotspot class, rather than each game having their own repeated implementations of them.
|
|
R2R SceneExt::display
|
|
|
|
This should help improve performance when scalers are being used.
|
|
|
|
|
|
|
|
Ringworld namespace
|
|
|
|
|
|
This splits checking if save and load are enabled to the individual game classes.
|
|
|
|
|
|
and Blue Force
This fixes bug #3422141, which was also caused by special checks introduced to try and handle Blue Force hotspots differently
|
