Erich/openttd - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2009-10-06	(svn r17720) -Codechange: guard the CargoPacket variables that are cached in ↵	rubidium
	CargoLists so they cannot be written from outside the CargoList class (based on patch by fonsinchen)
2009-08-21	(svn r17248) -Fix: add GPL license notice where appropriate	rubidium

2009-08-08	(svn r17113) -Change [FS#265][FS#2094][FS#2589]: apply the subsidy when ↵	smatz
	subsidy's destination is in station's catchment area and cargo packets originate from subsidy's source -Change [FS#1134]: subsidies aren't bound to stations after awarding anymore, they still apply to town or industry, no matter what station is used for loading and unloading. Awarded subsidies from older savegames are lost -Change [NoAI]: due to these changes, AISubsidy::GetSource and AISubsidy::GetDestination now return STATION_INVALID for awarded subsidies
2009-07-22	(svn r16914) -Codechange: split Station and BaseStation into different files	rubidium

2009-06-29	(svn r16694) -Fix [FS#2995] (rgradual loading, rnewindustries): only pay for ↵	rubidium
	whatever has been actually unloaded and perform the payment when unloading has finished. This fixes, amongst others: * cheating by starting to unload and after getting paid rushing to the depot to get sold (or unloading, loading and getting paid again for the remainder) * cargo being dropped onto a station at the moment a stockpiling industry doesn't accept it anymore * industries getting cargo that has not been unloaded yet and subsequently dumping it back on the station in one go Note: you will now get paid after the unloading has finished, so you'll have to wait a bit longer for 'your' money.
2009-05-29	(svn r16459) -Codechange: move definition of several cargopacket accessors ↵	smatz
	to header file
2009-05-22	(svn r16378) -Codechange: replace OldPool with simpler Pool. Compilation ↵	smatz
	time, binary size and run time (with asserts disabled) should be improved
2009-05-16	(svn r16325) -Codechange: replace GetPoolItem(index) by PoolItem::Get(index)	smatz

2009-01-31	(svn r15299) -Cleanup: remove many redundant includes	smatz

2009-01-04	(svn r14828) -Codechange: move most of save/load-specific code to separate files	smatz

2008-09-03	(svn r14235) -Fix (r14234): compilation with MSVC was broken	glx

2008-09-03	(svn r14234) -Fix: feeder share was computed wrong when splitting cargo packet	smatz

2008-08-23	(svn r14137) -Codechange: Remove a now unused member of CargoPacket	celestar

2008-06-27	(svn r13647) -Codechange: replace MAX_UVALUE() for std types with the ↵	skidd13
	equivalent constant
2008-05-04	(svn r12940) -Fix [FS#1974](r12913): [autoreplace] a vehicle backup should ↵	bjarni
	include the cargo packets in the vehicle as well
2008-04-06	(svn r12599) -Codechange: force AllocateSafeRaw() to be linked to simplify ↵	smatz
	compiler's decisions about inlining
2008-03-31	(svn r12489) -Codechange: split station.h into station_base.h and ↵	rubidium
	station_func.h.
2008-02-12	(svn r12120) -Cleanup: const-ify parameters when checking for same ↵	peter1138
	cargopacket source.
2007-08-30	(svn r11002) -Codechange: unhackify the cargo packet list saving (a little).	rubidium

2007-08-02	(svn r10749) -Codechange: use the generic pool item class as super class for ↵	rubidium
	cargo packets, which results in a nice reduction of code duplication.
2007-08-01	(svn r10743) -Fix: some typos introduces by copy-pasting.	rubidium

2007-07-01	(svn r10404) -Fix (r10266): Adding a cargo packet to cargo list could ↵	peter1138
	overflow. Now we detect this and just leave the cargo in its own packet.
2007-06-23	(svn r10297) -Codechange: increase the performance of ↵	rubidium
	CargoPacket::AllocateRaw using a very simple "caching" system.
2007-06-22	(svn r10266) -Codechange: keep track of the origin, time of travel and ↵	rubidium
	accumulated feeder share (transfers) of individual pieces of cargo. This means that cargo isn't thrown on a big pile when it's put in a station or unloaded at a station, however the GUI does not reflect these changes yet so you will not actually see it.