Uncomment "CrosshairColor" parsing code in config.c.
Untested, but LeoD says it works.
Original log file · 20120220-2375.txt
------------------------------------------------------------------------ r2375 | helixhorned | 2012-02-20 13:18:57 -0800 (Mon, 20 Feb 2012) | 3 lines Uncomment "CrosshairColor" parsing code in config.c. Untested, but LeoD says it works. ------------------------------------------------------------------------ r2374 | helixhorned | 2012-02-20 13:17:39 -0800 (Mon, 20 Feb 2012) | 4 lines Define Batoi/Batol to strtol(...) in compat.h and use these when necessary. That is, everyplace a user input is to be converted. The only remaining instance of atoi() is now atoi(s_buildDate). ------------------------------------------------------------------------ r2373 | helixhorned | 2012-02-20 11:54:24 -0800 (Mon, 20 Feb 2012) | 18 lines engine: make neartag accept a sprite-blacklist function and use it in sector.c. Internally, the last argument to neartag is now a pointer to a function int32_t (*blacklist_sprite_func)(int32_t i), which is supposed to return 1 if sprite[i] should NOT be considered for hitting. This is now used in the hard-coded neartag() calls in sector.c, but not in any way in CON (there's neither a C blacklist function provided, nor is there a possibility to define one in CON). There, all sprites with picnums >=1 and <=10 (i.e. the effectors) will be blacklisted. This remedies problems where such sprites would get in the way of switches. Note that a whitelist approach (only consider a predefined set, namely those picnums which will be checked afterwards) has back-compatibility implications since people may have used e.g. lotagged window sprites to cover a switch. Also, the >=1 to <=10 range is [sic] (the static, not dynamic values are used), since anyone redefining effector picnums is clearly out of their mind. ------------------------------------------------------------------------
Define Batoi/Batol to strtol(...) in compat.h and use these when necessary.
That is, everyplace a user input is to be converted. The only remaining instance of atoi() is now atoi(s_buildDate).
Already listed in build 2373
make neartag accept a sprite-blacklist function and use it in sector.c.
Internally, the last argument to neartag is now a pointer to a function int32_t (*blacklist_sprite_func)(int32_t i), which is supposed to return 1 if sprite[i] should NOT be considered for hitting. This is now used in the hard-coded neartag() calls in sector.c, but not in any way in CON (there's neither a C blacklist function provided, nor is there a possibility to define one in CON). There, all sprites with picnums >=1 and <=10 (i.e. the effectors) will be blacklisted. This remedies problems where such sprites would get in the way of switches. Note that a whitelist approach (only consider a predefined set, namely those picnums which will be checked afterwards) has back-compatibility implications since people may have used e.g. lotagged window sprites to cover a switch. Also, the >=1 to <=10 range is [sic] (the static, not dynamic values are used), since anyone redefining effector picnums is clearly out of their mind.