Fix: fmt's {:#04X} yields '0X00', not '0x0000'

Technically the 0X vs 0x is not a big problem, just not pretty. However, the
length also including the 0x results in unexpected behaviour, so it probably
better to not use it.
This commit is contained in:
Rubidium
2023-04-20 17:00:46 +02:00
committed by rubidium42
parent 27b4b5d0a0
commit 7b539fa7c9
5 changed files with 82 additions and 82 deletions

View File

@@ -117,17 +117,17 @@ public:
#else
# define LANDINFOD_LEVEL 1
#endif
Debug(misc, LANDINFOD_LEVEL, "TILE: {:#x} ({},{})", tile, TileX(tile), TileY(tile));
Debug(misc, LANDINFOD_LEVEL, "type = {:#x}", tile.type());
Debug(misc, LANDINFOD_LEVEL, "height = {:#x}", tile.height());
Debug(misc, LANDINFOD_LEVEL, "m1 = {:#x}", tile.m1());
Debug(misc, LANDINFOD_LEVEL, "m2 = {:#x}", tile.m2());
Debug(misc, LANDINFOD_LEVEL, "m3 = {:#x}", tile.m3());
Debug(misc, LANDINFOD_LEVEL, "m4 = {:#x}", tile.m4());
Debug(misc, LANDINFOD_LEVEL, "m5 = {:#x}", tile.m5());
Debug(misc, LANDINFOD_LEVEL, "m6 = {:#x}", tile.m6());
Debug(misc, LANDINFOD_LEVEL, "m7 = {:#x}", tile.m7());
Debug(misc, LANDINFOD_LEVEL, "m8 = {:#x}", tile.m8());
Debug(misc, LANDINFOD_LEVEL, "TILE: 0x{:x} ({},{})", tile, TileX(tile), TileY(tile));
Debug(misc, LANDINFOD_LEVEL, "type = 0x{:x}", tile.type());
Debug(misc, LANDINFOD_LEVEL, "height = 0x{:x}", tile.height());
Debug(misc, LANDINFOD_LEVEL, "m1 = 0x{:x}", tile.m1());
Debug(misc, LANDINFOD_LEVEL, "m2 = 0x{:x}", tile.m2());
Debug(misc, LANDINFOD_LEVEL, "m3 = 0x{:x}", tile.m3());
Debug(misc, LANDINFOD_LEVEL, "m4 = 0x{:x}", tile.m4());
Debug(misc, LANDINFOD_LEVEL, "m5 = 0x{:x}", tile.m5());
Debug(misc, LANDINFOD_LEVEL, "m6 = 0x{:x}", tile.m6());
Debug(misc, LANDINFOD_LEVEL, "m7 = 0x{:x}", tile.m7());
Debug(misc, LANDINFOD_LEVEL, "m8 = 0x{:x}", tile.m8());
#undef LANDINFOD_LEVEL
}