From: Erik V. <eri...@hc...> - 2005-10-04 22:00:48
|
> Erik - Can you take a look at how neighbors and entrances are > assigned and make sure they're correct? I think we're at a > point where we need to verify this is working correctly. > Even some of the hex painting code relies on checking neighbor hexes. These are model properties and therefore belong to game.MapHex. I have renamed the old model attribute to dummyModel and introduced MapHex model as an attribute of GUIHex. Each MapHex now knows its neighbours (all assigned in MapManager). If you click on a hex, the neighbours are shown in the console (I have tested this for 1830 and 1856). Impassibility and forbidden red and grey hex sides are not yet done. The former is easy. The latter needs a peek into the tiles themselves. Entrances are also dependent on the tile internals. I will do those things later. First TileSet.xml and Tiles.xml needs be read and turned into objects. I have not yet removed Hex and BattleHex, but these are no longer the real model since I introduced MapHex as the new model, a while ago. So IMO these will have to disappear one day. > I'm also thinking that rather than having a seperate property > for TileID, we should use the Label property that's already > there. Any thoughts here? Label is currently not used (and will IMO disappear with Hex). We do have Name and Id, and these two can be different, as the same tile numbers are sometimes used for different tiles in different games. Name is what is displayed (perhaps Label would be a better name, but I consistently use Name in all object types to avoid confusion), whereas Id is the number in the Tile Dictionary and must therefore be unique. For instance, 59 and 1059 are Ids of different tiles, both labelled 59. Erik. |