Just to summarise the bugs I'm aware of:

* Save games still don't work and haven't for a long time (at least
regarding sound). I'm looking at the sound part of this currently.

* _findfirst error message when saving/restoring games.

* Having the reverse_stereo variable specified in the config file causes a
crash on init_midi_device() where the heap appears to become corrupt.

* Cannot save under event sound server.
I need Christoph's help here with adding the extra variables that the event
sound server uses (and to remove the obsolete ticks_to_fade). Are there
instructions somewhere? Unfortunately there may not be a way to save a game
under the event sound server (for example) and then restore it under the
polled ss, since the last_played variable wouldn't be correct.

* Does the SDL full screen crash bug still exist?

Does Matt or anyone have comments or additions to this?

Regarding the memset in song.c: isn't it just good practice to clear a
struct before you use it, especially if not all of the struct's variables
are initially initialised (sic)?

Cheers!

Alex.


----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, December 10, 2001 9:56 AM
Subject: [freesci-develop] cvs: freesci


> CVSROOT: /var/cvs/freesci
> Module name: freesci
> Tesing username:
> Changes by: freesci 01/12/10 00:26:07
>
> Modified files:
> .              : ChangeLog THANKS TODO
> src/engine     : kgraphics.c kmenu.c
> src/include    : sciresource.h
> src/scicore    : Makefile.am resource.c resource_map.c
> src/sound      : sound.c
> Added files:
> src/scicore    : resource_patch.c
>
> Log message:
> * Added Robey Pointer to THANKS and the 'about' menu for hosting the BTS
(a)
> * Re-added support for resource patch files
> * song.c: Re-added the #ifdef SATISFY_PURIFY (b)
>
> (a) He maintains lag.net, which our bug tracker is now being hosted on
> (yes, it's back on-line!)
>
> (b): The idea is that this might trigger warnings on some tools when
> reading values that were not initialized properly. If there's a good
reason
> for doing the memset() always, it'd be OK to remove it again, of course.
>
> Revised TODO for 0.3.3 is done, all that remains is bug-fixing and
testing.
>
> (Actually, we wouldn't really need a release- all it'd be good for would
be
> to gather bug reports, and we have enought of these already ;-)
>
> -- Christoph
>
>
>





Reply via email to