Eliminate all 'variable ... set but not used [-Wunused-but-set-variable]'
warnings with GCC 4.6 except one in kplib.c
Original log file · 20111017-2079.txt
------------------------------------------------------------------------ r2079 | helixhorned | 2011-10-17 11:42:10 -0700 (Mon, 17 Oct 2011) | 2 lines Eliminate all 'variable ... set but not used [-Wunused-but-set-variable]' warnings with GCC 4.6 except one in kplib.c ------------------------------------------------------------------------ r2078 | helixhorned | 2011-10-17 11:41:38 -0700 (Mon, 17 Oct 2011) | 5 lines Make Polymer's FOV depend viewingrange variable in a 'tangent-linear' fashion. Among other things, this makes the FOV widening when shrunk work. User CON code should always check the initial viewingrange value when attempting to do FOV effects like zoom, because it is not guaranteed to be 65536 due to different screen aspect ratios etc. ------------------------------------------------------------------------ r2077 | helixhorned | 2011-10-17 11:41:17 -0700 (Mon, 17 Oct 2011) | 5 lines Two tweaks when keying in values directly in the editor's 3D mode. First, when pressing 'S on signed members (like the shade), display the real signed value instead of the value cast to an unsigned type. Second, when aiming at an overwall and pressing G, affect the overwall instead of the wall. Maybe these changes affect a few other queries too... ------------------------------------------------------------------------ r2076 | helixhorned | 2011-10-11 09:53:52 -0700 (Tue, 11 Oct 2011) | 1 line OSX build: don't include startup window (where the hell is the nib file?); makefile bits for libpng from maxports (dynamically linked, not enabled); update osxbuild.sh so that the 64-bit build links (statically) to libvpx ------------------------------------------------------------------------
Make Polymer's FOV depend viewingrange variable in a 'tangent-linear'
fashion. Among other things, this makes the FOV widening when shrunk work. User CON code should always check the initial viewingrange value when attempting to do FOV effects like zoom, because it is not guaranteed to be 65536 due to different screen aspect ratios etc.
Two tweaks when keying in values directly in the editor's 3D mode.
First, when pressing 'S on signed members (like the shade), display the real signed value instead of the value cast to an unsigned type. Second, when aiming at an overwall and pressing G, affect the overwall instead of the wall. Maybe these changes affect a few other queries too...
Already listed in build 2076