Rcet wrote:

You know how the image splitter splits the image up starting at 0,0? Could you possibly make it start at 1,1? It would be really great for using a big image for the HUD. like under New() you could put screen_loc = src.icon_state.

In hindsight, I think that the 1,1 notation would have been a better choice too, since it is a bit more consistent with similar notation elsewhere, but it's probably too late to make that change.

At any rate, I don't think it's a limitation. Your example is a pretty specific case, because it would really only work with big images that are already on the map, since they would have to have their icon-states set beforehand. And if that is the case, you can probably just use the map-location to set the screen_loc. In fact, I'm pretty sure Dan wrote a library to allow you to make HUDs in this fashion, drawing them on the map and then importing them over. The name and location of that library eludes me at the moment, but if you are interested let us know and we'll dig it up.

And you can always parse the icon_state string to get the coordinate out. There's an example of this in the reference entry for the icon_states() proc.