From: Erik V. <eri...@hc...> - 2006-07-08 22:39:23
|
> >I presume that, in case a city has more than one slot, > >slot center locations will be calculated from > >the Station position and the tile orientation. > >Can't we better specify these explicitly? > > > > > The tile code draws the entire city structure as one, and > only needs the > center point and orientation of the city structure. For hit > detection, > I suggest that simply saving the calculated position is better than > trying to store that in the XML data, espeially since zooming and > panning is going to change where it is drawn. Yes, but to drop tokens we need the slot center locations rather than the city location. > >And what is the use of "Category"? Just a simple way to > create annotation? > > > > > No, Category controls which tiles may be played there. For > example, in > 1830 the B tiles may only be played in Baltimore and Boston and also > control upgrades. At sufficient zoom levels, it should be > displayed on > the map as it is relevant to game play. That will work in many cases, but by far not all (for instance the Y hexes in 18Scan, to name just one example). The subject of having/not having default upgrade rules has been discussed in 18xx-softdev a few years ago, and the conclusion then was, that it would be best to specify all upgrades explicitly. At that time I was the main dissenter, but I have converted myself since. Hence: the TileSet.xml files now specify all allowed upgrades. I would prefer to keep it that way. > >Wouldn't preprinted Milano then also need drawing specifications > >to show the tracks joining? > > > > > That is the point of the exclude list, to show that the two > connections > join before the city and therefore can't be use simultaneously. Yes, for route calculation, but does the exclude also affect drawing that tile? Erik. |