Cosa è cambiato in EDuke32, build per build

last one + this one: A couple of tweaks against accidental overwriting of maps. - first, fix a bug where the map name wasn't reset to 'newboard.map' when starting a new map - When saving with Ctrl-S, query the user for confirmation and also show the file name where the map will be written - when going into the ESC-menu, print the file name where the map will be written on pressing 'S' above the '(S)ave' text

- first, fix a bug where

Keep in mind that MUSICANDSFXs with ambient sounds must still have lotags less than 999 because values >=1000 are used for the amount of reverb. (999 can't be used because the original code reads '< 999' and I'm not sure whether it has any special significance... probably not though)

cursor, query the mapper to pick one. The joining can still fail afterwards, which makes it only a semi-automatic helper feature.

allowed circle-walls started on the unconstrained _other_ side of a constrained wall. Also fix a potential invalid wall access when inserting a point (pretty serious, that!)

also for make-circle (C, SPACE). There's still a TROR corruption happening probably when inserting on constrained walls, but I've yet to get behind the real cause.

some wall drawing state is ripped out from overheadeditor() into a a file-scope struct (even if we don't yet need it there). If the deleting touches the first drawn point, the walls drawn so far are cleared.

overheadeditor() by allocating temp variables in the blocks where they are needed.

HOME or END in the user map selector. Now it's only one.

- fix arg checking in checkdefs.sh - some tilenum and quote ID validation in the CON interpreter - G_DrawDigiNum and friends: eliminate redundant strlen calls

We pack our own copy of glext.h to avoid build breakages on older environments, and having gl.h include its own was defeating all that.

ceilings or floors. In such cases, you're not squished unconditionally (instead of fetching the ceiling or floor height of the neighbor sector), but TROR isn't meant for small-scale RoR anyway.

polymer_addlight(). I have no idea whether it's the 'right' thing, but it fixes this: Conditional jump or move depends on uninitialised value(s) at polymer_updatelights (polymer.c:5090) by polymer_drawrooms (polymer.c:938) . . . Uninitialised value was created by a stack allocation at loadmaphack (engine.c:9482) Fix another uninitialized access when rendering jpegs.

This fixes a crash when loading a map afterwards. Tweak a few debugging messages and some whitespace.

Also move a 'int16_t editstatus' declaration from polymost.c to engine_priv.h.

My choice of solution is simply to add an extra set of values duplicating the previous five because doing so would definitely show the user no changes. I could have tinkered with the messy loop where the out-of-bounds references are made but there is no guarantee I could have succeeded or kept compatibility.

Getting the texture handles without requiring invalidation means we can handle ART-animating tilenums without impacting performance too much.

Polymer has a hack that snaps horiz values of spotlights between 90 and 110 to 90 and 110 to avoid triggering aliasing artifacts with perfectly horizontal spotlights. Propagate that change all the way to the spotlight SE sprite so that the code won't think that the horiz is always different from the light and mark it invalid each frame.

We need to Y-invert the projection texcoords when sampling from the lightmap.

Sprites would stick with their old material on global palette change. This goes through all prsprites and clobbers their CRCs so that an alternate skin / tint / highpal can be applied accordingly.

the nextwall pointers correctly; Add some 'asksave=1' and 'make old-nextwalls invalid'.