> ----- Original Message ----- > From: "Christian Ohm" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Sunday, December 03, 2006 3:51 AM > Subject: Re: [Warzone-dev] Backporting fixes for 2.0.5? > > > On Saturday, 2 December 2006 at 19:11, Dennis Schridde wrote: > >> Am Samstag, 2. Dezember 2006 18:51 schrieb Christian Ohm: > >> > There have been quite a few patches fixing things, or adding small > >> > features while touching only a few lines of code in the trunk (the > >> > playlist fix, and the SDL_QUIT and gamma patches, for example). Any > >> > plans to apply those to 2.0 as well? > >> > >> Go for it... ;) > >> Actually it was not directly planed, but if someone wants to do it... > > > > I had a look at the SVN changelog. In most cases, I don't know if the > > fix applies to 2.0 as well or just a new feature. And there are quite a > > few patches where I can't find the supposed fix in the remaining > > changes, so the original author might want to have a look: > > > > r371: Fixed script compilation bugs > > > > r383: Remove an unnecessary and wrong cast > > applies > > > > r386: Disabled "Allied players send vision to each other automatically > > (only once)" for "Allow alliances" alliance mode > > > > r397: Correct openal buffer > > applies, but needs another change > > > > r405: Fixed difficulty slider applying settings to the wrong players > > r407: Fixed disabled AIs showing up in the game > > r411: fixed and enabled shared ally vision for TEAMPLAY and 'Locked > > Teams' modes > > fixed disabled players allying their team members > > r413: Fixed double messages in online games > > r415: Fixed AIs getting renamed when changing player number in MP games. > > Prevented NETbcast() from flooding the log in games with no network > > communication. > > orderDroidObj() scripting function will no longer cause ASSERT when > > DORDER_DROIDPERAIR is passed as parameter. > > r422: It is now possible to win in a team in 'Locked Alliances' mode, > > also in this mode a player doesn't lose until all of his team members > > were defeated > > Game now shows a text message when player has won/lost the game > > (just a temporary solution to bug #7317) > > Added extra heap debug, should be there at least until we fix bug > > #6530, as PTRVALID() doesn't seem to detect corrupted DROID pointers on > > win > > Increased number of iterations A* is allowed to do per frame, which > > will hopefully speed up pathfinding > > Fixed multiplayer menu slider bug (bug #6529) > > Fixed players not forwarding enemy units visibility to their allies > > in 'TEAMPLAY' and 'Locked Alliances' modes > > r424: Re-enabled some debug keys and disabled unused ones > > > > r427: Process SDL_QUIT > > applies > > > > r428, r430, r508: Add gamma controls > > combined patch may be attached > > > > r436: fixed implicit bool/int to string convertion for the scripting > > language > > minor scripting function fixes > > r440: Make lots of __inline, _inline, FUNCINLINE and whatnot static > > inline. See bug#7591 > > r448: Fixed double declaration of "FUNCTION" token for bison > > > > r451: resolution config value has been changed to width and height > > (easier to parse). I probably forgot to tell that I changed the > > --viewport cl option to --resolution, which should be more clear to non > > programmers needs parts of the previous one as well. I think we should > > use > > --resolution in 2.0 as well, so we do not need to document the different > > versions. > > > > r452: Report wrong tracknumbers to LOG_SOUND and don't crash in > > sound_Play*DTrack > > Correct --help text > > Make console backlog key configurable > > > > r459: HP/Reload bars overlaping > > only for multi-turret? > > > > r460: commander-related crash fix > > r472: sensorcrash.patch: fixes a crash when repairing a not damaged > > command center, corrects the mouse cursor > > > > r474: Fix for bug #7708: isHumanPlayer() now checks for player numbers > > outside the range if [0,MAX_PLAYERS) > > applies > > > > r492: License clarification about original data files > > add this or whatever we decide on > > > > r499: fixes disappearing oil derricks (bug #7740) > > > > r501: Fix typos in COMPILE and remove outdated COMPILE.html > > plus check other docs > > > > r502: Check for '\r' as well as '\n'. This should make playlists with DOS > > line endings work > > applies > > > > r511: Attempt to fix a script callback bug as described on IRC > > r515: Fixed target prediction finally > > Fixed a bug which prevents AA weapon area of effect damage from > > working properly > > Fixed crashes when firing at baba people,baba vehicle in > > singleplayer campaign > > r517: Fixed a potential crash with transport > > Fixed a crash/repair units disorder when linked to a commander > > None of my commits apply to 2.0. Most of what I have done will have to wait > until 2.1 or later. If time will permit I will take a closer look at the > bugfixes, although most of them seem to apply to the features to be > released in 2.1. > > Troman That's what I expected... Christian: You can try and see what bugfixes seem to apply and make sense, but I think that most of them will be either not related to any issues in 2.0 or might be hard to apply. Generally I don't want to delay 2.0.5 any longer because of this. (Yes, the licensing-letter needs to be send before and and and, so if you get those fixes into 2.0, without adding the new features that might come along with those commits, then feel free to do it. ;) )
--Dennis
pgp2cmMaTAAnV.pgp
Description: PGP signature
_______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
