>If no one comes up with a better solution I will color-code the targets and
>perform a getPixel under the moving object, thus I know over which target
>the object is. The disadvantage of this is that the way the targets are
>designed is somewhat limited.
>
>Thanks for telling me the ohter ways to solve the problem.


I don't think I did, did I? My question about whether you just needed 
to know which country you clicked in was with using color mapping and 
getpixel in mind, but not the way you're talking about, which would 
have the obvious design consequence.

Instead of making your nice map look ugly, make a second copy of the 
map, and make that extremely ugly. Make each different area be a 
totally flat color, no anti-aliasing between areas, and make it 8 
bit. That would be enough for 256 different areas. When you quad the 
nice looking map, also quad the same part of the 8 bit image, and 
then getpixel from its quad output to find out which area the user 
clicked on.

The other solutions I was thinking about, but are no better than the 
getpixel approach, were to either have a 3D sprite or a quadded 
bitmap sat under the sprite you have. You could then use either 
modelsunderloc with detailed on to get an isectposition for you to 
know where they clicked, or you could use mapStageToMember on the 
bitmap. In both cases the sprite in question wouldn't be seen by the 
user (the 3D member would be non-dts), but the ideas are overkill 
compared to the getpixel approach, which can work extremely well.

[To remove yourself from this list, or to change to digest mode, go to 
http://www.penworks.com/lingo-l.cgi  To post messages to the list, email 
[EMAIL PROTECTED]  (Problems, email [EMAIL PROTECTED]). Lingo-L is for 
learning and helping with programming Lingo.  Thanks!]

Reply via email to