Ah... I hastily pushed that. Right when I went to use it in line(), I realized... The pixel math from red blob is for 2d hexagons, so I can't just add my T to the height.
T would be represented by one pixel in height. That's the vertical side. The horizontal sides would be skewed for the pseudo-3D presentation. In the math, those sides are the same length as the height, but in pixels... it's complicated.
I don't actually need to calculate pseudo-3d pixel position right now. In fact, I might not need to at all. I could just draw the hexes on the screen and listen for mouse click events. Whatever tool I use would probably tell me, "Hey. He clicked on this hex sprite. This one. It has these axial coordinates." So I don't think I'd have to convert pixel to hex in most cases.
So... remove that bad math from the From<Point> bit in PixelPoint.
Ah... I hastily pushed that. Right when I went to use it in line(), I realized... The pixel math from red blob is for 2d hexagons, so I can't just add my T to the height.
T would be represented by one pixel in height. That's the vertical side. The horizontal sides would be skewed for the pseudo-3D presentation. In the math, those sides are the same length as the height, but in pixels... it's complicated.
I don't actually need to calculate pseudo-3d pixel position right now. In fact, I might not need to at all. I could just draw the hexes on the screen and listen for mouse click events. Whatever tool I use would probably tell me, "Hey. He clicked on this hex sprite. This one. It has these axial coordinates." So I don't think I'd have to convert pixel to hex in most cases.
So... remove that bad math from the
From<Point>bit in PixelPoint.