On Oct 12, 12:25 pm, Benjamin Mottram <
b.b.a.mott...@googlemail.com>
wrote:
> Hi Larry.
>
> Thanks for the advice. Actually I had considered the fusion table and
> KML route, but I suppose I should be more specific about my particular
> challenge.
>
> The hex grid is part of game iam making for my degree, and I will be
> honest I am still fairly new to programming so if i gloss over stuff
> or miss out the obvious please do accept my apologies in advance.
>
> The hex grid does indeed need to be clickable. The idea being that
> the "state" of the hex will change as each turn of the game progresses
> (for example change colour). So I was considering that each hex
> should be created at its own object?
>
> So I suppose it will need
> -to deal with mouse click/over events.
From your description above, you only talk about click events.
KmlLayer and FusionTablesLayer both handle click events, but not
mouseover events.
> -so that each individual hex can be identified as a unique coordinate
> in an x,y grid.
I'm not sure what that means, do you want to identify the particular
hexagon that was clicked on? If that is the case, you can do that
with KmlLayer or FusionTablesLayer or a polygon.
> -and that each hex can be treated as an object and have its attributes
> changed.
That you might be able to do with the styling options on a
FusionTablesLayer, you won't be able to do it with KmlLayer unless you
dynamically create the kml.
>
> That has massively complicated things... What is the best approach do
> you believe?
That is up to you. If the hex grid isn't too big, polygons might be
the simplest.
Is the hex grid going to be fixed to the earth, or might it need to
move?
-- Larry