Clear the confusing usage of NUM_MAX_VAR (It's 255 actually, not 256).

svn-id: r33339
This commit is contained in:
Kari Salminen 2008-07-27 14:36:53 +00:00
parent 955d0700f5
commit cedbb6b2b2
2 changed files with 3 additions and 3 deletions

View File

@ -50,7 +50,7 @@ struct overlay {
};
#define NUM_MAX_OBJECT 255
#define NUM_MAX_VAR 256
#define NUM_MAX_VAR 255
extern objectStruct objectTable[NUM_MAX_OBJECT];

View File

@ -535,7 +535,7 @@ bool CineEngine::loadPlainSaveFW(Common::SeekableReadStream &in, CineSaveGameFor
renderer->restorePalette(in);
// At 0x2083 (i.e. 0x2043 + 16 * 2 * 2):
globalVars.load(in, NUM_MAX_VAR - 1);
globalVars.load(in, NUM_MAX_VAR);
// At 0x2281 (i.e. 0x2083 + 255 * 2):
for (i = 0; i < 16; i++) {
@ -733,7 +733,7 @@ void makeSave(char *saveFileName) {
renderer->savePalette(*fHandle);
globalVars.save(*fHandle, NUM_MAX_VAR - 1);
globalVars.save(*fHandle, NUM_MAX_VAR);
for (i = 0; i < 16; i++) {
fHandle->writeUint16BE(zoneData[i]);