| Age | Commit message (Collapse) | Author |
|---|
|
declaration)
|
|
Last occurence of FindLandscapeTile in the tile-specific functions gone. Thanks to Tron for doing lots of work in this direction
|
|
ground types (including roadworks).
|
|
|
|
|
|
(Pointed out by peter1138)
|
|
|
|
Although it was an accessor, nor his usage nor the values were clear.
|
|
|
|
|
|
|
|
code and proofreading, thanks to peter1138 for another lot of code and ideas.
|
|
|
|
put and get the status of a level crossing
|
|
from a tile
|
|
|
|
|
|
|
|
|
|
|
|
get information about rail tiles
|
|
|
|
shiny new functions and mark some strange constructs with XXX
|
|
road) under bridges
|
|
|
|
|
|
magic numbers by enums and some related changes
|
|
deem it unnecessary
|
|
|
|
|
|
a level crossing by some less magic numbers
|
|
code by using them
|
|
which direction a pieces of rail goes
|
|
tile/depot/waypoint. This is just a tiny step, the rail code needs way more love and caring
|
|
|
|
level crossing or a road depot
|
|
road types and pieces
|
|
if a level crossing is on a sloped tile, it has to be on a level foundation
|
|
-Fix: Correctly restore the roadside after roadworks are finished
|
|
|
|
|
|
road pieces
|
|
in r3655
|
|
|
|
|
|
|
|
|
|
it was just a complicated way of writing GetTileSlope(tile, NULL)
|
|
add consts, reduce indentation level by short-circuit logic, convert if cascades to switch, whitespace, bracing, plus some minor stuff
|
|
- Don't treat non-booleans as booleans
- Reduce variable scope
- Bracing
- Use DeMorgan's law to make conditionals easier to read
- if cascade -> switch
- Replace some magic numbers by symbolic names
- Avoid assignments within other statements
|
