Defining areas for mouselistener in Java?

Well, I have to code a risk clone in java (yes, fail) and I need the program to select the province when clicked on - so I need to define these areas some way. My idiot instructor suggested that I add every pixel manually, and I happen to prefer dying over it.

I am sure there is a more intelligent way, but does anyone know?

who cares

use polygons

Use a bitmap with region 1 in colour 1, region 2 in colour 2, etc. for lookup. Polygons are fine, too.

you have a bitmap of each region. you know where you place it. To iterate through all the bitmaps and check to see if your click was there is not hard. Fuck you guys are such retards.

>>1
Use color keys, i.e. what >>4 said.
Oh, wait. You said Java?

Well then, you want to define a class hierarchy for geometric information, like (all classes):

Geometry (abstract)
    Geometry2D (abstract)
        GeometricShapes (abstract)
            Polygon (holds a list of Axis)
                Triangle (for convenience)
                Square (for convenience)
                RegularPolygon
                    RegularTriangle (for convenience)
        Geometry2DTypes (abstract)
            Point
            Axis (aggregates 2 Point)

Well, this was actually a stub. The final implementation will most surely implement more classes, as well as a few interfaces to describe geometry.

Then you define methods for creating these shapes, associate them to objects describing your provinces (again, under a class hierarchy to model universes, galaxies, solar systems, planets, continents, countries, states, autonomous communities, provinces, counties, towns, neighbourhoods, residential and other types of areas and parcels), and find whether a point you recover from mouse information, casted or recreated as a geometric point and contemplating a certain offset (which you may model as inherited properties in the geometry class hierarchy somehow) will belong to an area.

That would be appropriate for a Java job.

>>5
shit solution

>>4
good, simple solution

>>3
might work if the area boundraries are simple, but you'd still need to iterate so it's not much better than >>5

Geometry YOU BITCH IDIOT.