Update of /cvsroot/netrek/client/netrekxp/resources/docs
In directory sc8-pr-cvs7.sourceforge.net:/tmp/cvs-serv9974/resources/docs

Modified Files:
        changes.txt 
Log Message:
Change from Multithreaded to Multithreaded DLL runtime library, involved adding 
a
few headers, and commenting out the perror() and getpid() function definitions 
as they
seem to be built in now.  Also removed libcmt.lib from import libs.
Removed unused UPDATE define.
Changed WARNTIME and MESSTIME to use tenths of seconds rather than updates/sec,
so warning messages don't disappear too fast at higher FPS rates.
Moved j->p_explode out of draw if check, so that explosion counter updates even 
at low
update rates.
Reworked logic for phaser, torp and plasma fuses.  Sets a minimum fuse and 
updatefuse length
so even at low update rates, these weapons draw on screen.  Also changed sound 
logic so
that sound events play proper at all update rates.  Also fixes a bug where 
frame could fall
outside range of bitmaps, causing errors.  Frame is now reset within the bounds 
of the bitmap
definition number of frames.  Showed up as a problem at low updates/sec rates.

Index: changes.txt
===================================================================
RCS file: /cvsroot/netrek/client/netrekxp/resources/docs/changes.txt,v
retrieving revision 1.111
retrieving revision 1.112
diff -u -d -r1.111 -r1.112
--- changes.txt 25 Feb 2007 14:12:09 -0000      1.111
+++ changes.txt 26 Feb 2007 06:54:48 -0000      1.112
@@ -1,4 +1,5 @@
 Netrek XP 2006, Version 1.2: (Released Feb-2007)
+- changed warning message timer to be in tenths of seconds rather than 
updates/sec
 - changed keepInfo netrekrc option from updates to tenths of seconds, so info 
wins
   remain up at a controllable time regardless of server update rate
 - full support for server FPS feature, allowing client to receive up to 50 
updates/second!


_______________________________________________
netrek-cvs mailing list
[email protected]
http://mailman.us.netrek.org/mailman/listinfo/netrek-cvs

Reply via email to