rubidium [Wed, 27 Jun 2007 18:53:24 +0000] rev 7093
(svn r10360) -Fix (r10359): make should always do "make all" by default
rubidium [Wed, 27 Jun 2007 18:50:18 +0000] rev 7092
(svn r10359) -Codechange [FS#935]: add some explanations what the different make "commands" do.
rubidium [Wed, 27 Jun 2007 17:19:05 +0000] rev 7091
(svn r10358) -Codechange: remove the cargopacket leakchecker as it never asserted in almost a week of stresstesting, so I'm pretty sure all cornercases are tested by now.
rubidium [Wed, 27 Jun 2007 17:05:06 +0000] rev 7090
(svn r10357) -Fix: and when we're at it... yet another memory leak, but only when you start a new game; can't find any other memory leaks we can fix.
rubidium [Wed, 27 Jun 2007 16:54:50 +0000] rev 7089
(svn r10356) -Fix (r10143): another memory leak eliminated.
rubidium [Wed, 27 Jun 2007 16:41:37 +0000] rev 7088
(svn r10355) -Fix (r10092): memory leak when encoding (reading) sprites.
rubidium [Wed, 27 Jun 2007 14:37:46 +0000] rev 7087
(svn r10354) -Fix [FS#950]: loading indicator showed "^" when the train would load at the given station.
rubidium [Wed, 27 Jun 2007 14:15:48 +0000] rev 7086
(svn r10353) -Fix/Feature [FS#669]: disallow (in the GUI) the building of infrastructure you do not have available vehicles for. This means that the airport building button is disabled till you can actually build aircraft. The game itself will not disallow you to build the infrastructure and this "new" behaviour can be overriden with a patch setting.
rubidium [Wed, 27 Jun 2007 10:02:55 +0000] rev 7085
(svn r10352) -Fix: the network did not request the newgrf names of newgrfs that it couldn't find; it only wanted to request the newgrf names of newgrfs that where available locally and than were called "<Unknown>".
KUDr [Tue, 26 Jun 2007 22:29:52 +0000] rev 7084
(svn r10349) -Fix [FS#941, YAPF, r10301]: tile/trackdir must be used as node key and also as segment key in the cache (SmatZ).
In the past it was possible to use tile/exitdir as the key because segments beginning on the same tile/exitdir were incorrectly considered the same. What I still don't understand is why this bug happened only on 64 bit systems (linux, Win64).