| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2014-01-19 | (svn r26267) -Fix [FS#5865]: Really fix the infinite recursion problem and ↵ | fonsinchen | |
| always consider all branches of conditional orders as possible next stopping stations. | |||
| 2014-01-16 | (svn r26263) -Fix [FS#5865]: Don't run into infinite recursion when getting ↵ | fonsinchen | |
| next stopping station | |||
| 2013-10-20 | (svn r25891) -Feature: Use smallstack to allow for multiple next hops when ↵ | fonsinchen | |
| loading and unloading. | |||
| 2013-08-20 | (svn r25736) -Codechange: move condition prediction out of ↵ | fonsinchen | |
| GetNextStoppingOrder so that we can access both branches in calling code | |||
| 2013-08-11 | (svn r25718) -Fix: return INVALID from GetNextStoppingStation if vehicle ↵ | fonsinchen | |
| would have to unload everything at this same station at the next stop | |||
| 2013-07-05 | (svn r25562) -Fix [FS#5633]: If the next order cannot be resolved, reset the ↵ | frosch | |
| current order property instead of leaving it in an intermediate state. | |||
| 2013-06-09 | (svn r25361) -Feature: distribute cargo according to plan given by linkgraph | fonsinchen | |
| 2013-05-19 | (svn r25259) -Codechange: track capacities and usage of links | rubidium | |
| 2013-02-24 | (svn r25041) -Remove [FS#3764-ish]: ordered refit with subtypes, since the ↵ | frosch | |
| cases where it worked were corner cases rather than the general case. | |||
| 2013-02-14 | (svn r24995) -Codechange: Add flags to vehicle service interval for custom & ↵ | rubidium | |
| ispercent (peter1138) | |||
| 2013-01-23 | (svn r24936) -Fix [FS#5446]: Don't allow order refit to be set for no-load ↵ | peter1138 | |
| orders. | |||
| 2013-01-08 | (svn r24900) -Fix [FS#5389]: Comments with typos (most fixes supplied by ↵ | planetmaker | |
| Eagle_rainbow) | |||
| 2012-12-20 | (svn r24833) -Codechange: Replace magic numbers for invalidating ↵ | michi_cc | |
| vehicle-related windows with an enum. | |||
| 2012-08-03 | (svn r24457) -Fix [FS#5264] (r23087): Changing auto-refit for a 'goto ↵ | michi_cc | |
| station' order was inadvertently modifying the full load state. | |||
| 2012-07-09 | (svn r24390) -Change [FS#5213]: Allow cloning of orders which are ↵ | frosch | |
| unreachable for the destination vehicle if they were already unreachable for the source vehicle. This makes cloning/autorenewing/autoreplacing behave more smooth during station reconstruction. | |||
| 2012-05-26 | (svn r24282) -Codechange: Add AddVehicleAdviceNewsItem function to ↵ | frosch | |
| preemptively deduplicate code. | |||
| 2012-04-01 | (svn r24086) -Fix [FS#5131] (r23504): Cloning orders of aircraft with ↵ | frosch | |
| limited range failed. | |||
| 2012-02-14 | (svn r23947) -Feature: Timetabled maximum travel speeds for non-flying vehicles. | michi_cc | |
| 2012-01-27 | (svn r23859) -Fix: Inserting conditional orders for ships checked the wrong ↵ | frosch | |
| orders wrt. maximum distance. | |||
| 2012-01-25 | (svn r23849) -Fix [FS#5008]: when the network is lagging, you try to copy a ↵ | rubidium | |
| vehicle's order but accidentally create a station order and then copy the vehicle's order (before the first command is executed) one could trigger an assertion from the pool. Simplify the ancient code and make it more fool proof, even though it could stop copying a vehicle's orders slightly earlier than it would now... but who has come near that limit and really needed that many orders? | |||
| 2012-01-03 | (svn r23740) -Codechange: remove some 300 unneeded includes from the .cpp files | rubidium | |
| 2011-12-13 | (svn r23511) -Fix [FS#4885] (r23504): Aircraft orders could not be shared ↵ | planetmaker | |
| anymore when they had no range property declared (Hirundo) | |||
| 2011-12-13 | (svn r23505) -Add: Indication in the order list if the next destination of ↵ | michi_cc | |
| an order is out of range. | |||
| 2011-12-13 | (svn r23504) -Feature: Aircraft range. | michi_cc | |
| 2011-12-09 | (svn r23464) -Fix [FS#4876]: clear the backed up orders of a removed station ↵ | rubidium | |
| as well, otherwise one could create orders to a station that was never in the original backupped orders. For example a road vehicle trying to go to a buoy. | |||
| 2011-11-12 | (svn r23199) -Fix [FS#4822]: oil rigs that "expired" did not get removed ↵ | rubidium | |
| from the station list | |||
| 2011-11-04 | (svn r23087) -Feature: Auto-refitting of vehicles during loading at a ↵ | michi_cc | |
| station when the vehicle allows it. | |||
| 2011-08-30 | (svn r22858) -Feature: Conditional order depending on remaining lifetime of ↵ | frosch | |
| a vehicle. (monoid) | |||
| 2011-08-26 | (svn r22845) -Fix [FS#4745]: perform stricter checks on some commands (monoid) | rubidium | |
| 2011-07-02 | (svn r22620) -Change [FS#4651]: Enforce refit orders to be 'always go to ↵ | frosch | |
| depot' orders; service-only and stop-in-depot orders make no sense with refitting. | |||
| 2011-06-14 | (svn r22589) -Fix [FS#4641]: PBS order forecasting modified the current ↵ | frosch | |
| order index in case of a goto-nearest-depot order and no depot could be found. | |||
| 2011-05-18 | (svn r22473) -Codechange: Automatic orders are better called implicit orders ↵ | planetmaker | |
| as no real order influencing path finding is added | |||
| 2011-04-16 | (svn r22331) -Change: When inserting an (automatic) order A in front of an ↵ | frosch | |
| order B, disable modifications of automatic orders for all vehicles currently heading for B as we do not know whether they will reach A or B first. (except for the vehicle causing the insertion of the automatic order itself) | |||
| 2011-04-16 | (svn r22330) -Change: When a conditional order triggers and causes skipping ↵ | frosch | |
| to a particular order, disable modifications to automatic orders. till reaching the next real order, as we do not know whether to change the targets of conditional orders when inserting automatic orders. (So, when the vehicle skips to an order and later inserts an automatic order, the conditional order will still point to the same order, so the automatic order will be inserted again the next time.) | |||
| 2011-04-16 | (svn r22326) -Fix: Destinations of conditional orders were update ↵ | frosch | |
| incorrectly when deleting orders in front of the conditional orders, if the target order wwas the order just before of the conditional order. | |||
| 2011-03-05 | (svn r22200) -Fix (r21642): removing a station order could stop when ↵ | smatz | |
| removing first automatic order | |||
| 2011-02-19 | (svn r22116) -Codechange: use PoolBase::Clean() at more places | smatz | |
| 2011-02-18 | (svn r22105) -Fix: crash when copying an orderlist to a vehicle that already ↵ | yexo | |
| had orders | |||
| 2011-02-09 | (svn r22046) -Fix [FS#4487]: Make sure order indices stay in range when ↵ | frosch | |
| copying, sharing, unsharing or deleting all orders. | |||
| 2011-02-09 | (svn r22045) -Codechange: Move cancelling the current loading order on ↵ | frosch | |
| deleting the current order to a separate function. | |||
| 2011-02-08 | (svn r22024) -Fix [FS#4468]: verify we can allocate an OrderList before we ↵ | smatz | |
| actually try to do so (Rubidium) | |||
| 2011-02-07 | (svn r22021) -Fix (r22019): ofcourse make doesn't notice files are gone, so ↵ | rubidium | |
| it doesn't recompile everything that needs to be recompiled... | |||
| 2011-02-04 | (svn r21961) -Remove: limitation that not loading and not unloading is ↵ | rubidium | |
| mutual exclusive | |||
| 2011-01-31 | (svn r21934) -Fix (r21933): The original plan was to run the regression ↵ | frosch | |
| before committing. | |||
| 2011-01-31 | (svn r21933) -Codechange: Split cur_order_index into cur_auto_order_index ↵ | frosch | |
| and cur_real_order_index to keep track of the current real order in an unambiguous way. -Fix [FS#4440]: Automatic orders behave now stable wrt. service orders and are not added or removed depending on the need of servicing. -Fix: Various other issues with automatic orders, e.g. vehicles getting stuck with "no orders" when there are automatic orders at the end of the order list. | |||
| 2011-01-18 | (svn r21846) -Codechange: move documentation towards the code to make it ↵ | rubidium | |
| more likely to be updated [o-s]. | |||
| 2011-01-15 | (svn r21809) -Fix [FS#4404]: remove unreached automatic orders as well when ↵ | rubidium | |
| reaching an ordered waypoint or depot (fonsinchen) | |||
| 2011-01-09 | (svn r21744) -Fix: Allow Ctrl+Clicking automatic orders for scrolling to ↵ | frosch | |
| their destination. | |||
| 2011-01-07 | (svn r21739) -Fix [FS#4388] (r19657): make clearing refit orders work again | rubidium | |
| 2011-01-06 | (svn r21737) -Fix (r1)[FS#4384-ish]: A loading order was also marked as 'not ↵ | frosch | |
| part of orders' when the order before the current order was deleted. | |||
 |
index : Erich/openttd | |
| Unnamed repository; edit this file 'description' to name the repository. |
| summaryrefslogtreecommitdiff |