Bug #2812694: "CINE: Operation Stealth german crash". Our code
assumed that there exists only 256-color version which is not
the case for German version. Added code to store background
format. Old savegames are broken and could not be fixed.
Bumped savefile version.
svn-id: r49699
Now AD can search nested directories. By default it is turned off,
but there is new parameter to ADParameters struct. Usually value
of 2 is good enough for all purposes.
svn-id: r49653
These functions are only used internally be Engine subclasses, and
by moving them to a separate header we can reduce indirect header
dependencies.
svn-id: r48934
This removes the dependency on array.h from str.h.
Also, begun migration from the confusing type name "StringList" to
the more appropriate StringArray.
svn-id: r48282
With the latest changes to executePlayerInput we
should now be able to free the girl at the bottom of the
ocean without the r33872.
The commit log from r33872 was:
"Fix for bugging moving at the bottom of the ocean when trying to free the girl from the ropes and swimming to the surface. Some global variables related to mouse position weren't being updated in executePlayerInput, now they are and things seem to work. Also enables moving in the labyrinth arcade sequence at the palace."
svn-id: r47516
- NOTE: This doesn't seem to work correctly yet.
My current guess is that it has to do with how
some keyboard events are handled in cine/main_loop.cpp's
processEvent-function and some in cine/various.cpp's
executePlayerInput.
svn-id: r47515
Additionally:
- Operation Stealth specific: Make makeActionMenu() use canUseOnItemTable.
This would seem to be the correct way according to disassembly
(Although there is of course a possibility that I have overlooked
some part of the code).
svn-id: r47508
- Combines mouse position and button state fetching
from two branches (allowPlayerInput / !allowPlayerInput)
into a single loop with a little more exotic while-clause.
NOTE! Added manageEvents-call into the unified version although
there was no manageEvents-call in one of the versions that was
combined. Tested a little and didn't seem to matter, but hopefully
won't cause any regressions!
- Limit first possible 'renderer->setCommand(commandBuffer)' call
to Future Wars only (Checked with FW & OS disassembly).
- Combined all cases of 'left and right mouse buttons are down'
into a single if-clause (All those cases call makeSystemMenu).
svn-id: r47505
This makes sense as a default for CLUT8 modes, but not really
for anything else. As part of the gsoc2009-16bit merge, the
default was changed to "all ones", with extra code in the SDL
backend to truncate this to the depth of the mode. However,
"all ones" (white) still isn't a very useful default for RGB modes.
So rather than jumping through hoops to provide a bad default,
it's better to remove the default altogether. Engines which relied
on the old default of 255 have been updated to specify it explicitly.
svn-id: r47118
