Technically, images do have a screen_loc variable. Also technically, adding them to client.screen gives an error, so it's not a particularly useful variable. Of course, images are just as much objects as objs are, so there aren't really any efficiencies in using them over objs.

The best solution is just to keep a global list of letters which have been created and are no longer being used. Remove from the list when you need some letters, add to it when you're done with them, and only create new objects if you need a new one and the list is empty.

Garthor wrote:

Of course, images are just as much objects as objs are, so there aren't really any efficiencies in using them over objs.

at least it could be better 0.001%.

The best solution is just to keep a global list of letters which have been created and are no longer being used. Remove from the list when you need some letters, add to it when you're done with them, and only create new objects if you need a new one and the list is empty.

lol.But HUDs are not global.Each player has a HUD.And even if u mean creating the list for each player, then it could be more reasonable.But it shouldn't make much a difference as I am showing messages on the HUD which may take up all the 26 letters in the alphabets, but better than not doing so.

Soul Sign wrote:

1.Create a Single Object and place it in the HUD.
2.Add images to it as overlay,since images do support pixel_x and pixel_y on screen.

Any other Better Ideas?

The way you have it, a good amount of activity within the game using this way, will create some CPU usage that you'll most likely not want.

You could make a list for the client (not mob, since mobs can be switched in-game, thus causing the list to be re-read or whatnot) containing every Number/Letter/Character /obj that you want, then adding them to their map screen when needed. This way, no real new /obj's are created, they are just added/removed.
I haven't tried that way, but I will later on down the road.

Soul Sign wrote:

Thats not what Lummox JR would say.He would say 'client' simply because making a list for each and every mob who need not be under a client can use up BYOND's resources.

Did I not say, "You could make a list for the client..." ?
Same thing as "He would say 'client'..."

What you said was exactly as Garthor said(except for the point that you didn't consider multiple letter usage).

That's a matter of you configuring it to your specifications.
Ex; If you want the word "Hello" at the bottom of your map, you'll need to display the letter H, then gather the position of H and calculate the next position for the next symbol and so on. I thought that was just enough common sense and I didn't have to say that.

You'll have less power over images (I'll assume you mean /image) since you can't directly change pixel_x/pixel_y, screen_loc and etc. They are just images and aren't actual objects that can be modified.
/obj would be more powerful in this case, and the combination with making it a client list (Like I said and you said LummoxJr would suggest) because client.mob can change within the game, causing it to run mob/Login(), mob/Logout() which would involve you removing the screen text or whatever, and then re-adding it. With a client list, you can easily gather client.mob's information (if using it for statistics or whatnot) and adjusting the already existent screen text to update.
Either way, you'll want client list, and my recommendations for /obj instead of /image, for less limitations/complications and potentially less CPU usage.

EDIT:
Oh, I didn't seem to catch what you meant by multiple usages until now. I apologize, my brain is a bit confuggled from coming out of Summer Classes like Calculus.
So yeah, you'll probably want to go with generating new /obj still, unless you can comprehend enough to alter /image.
That, or you could create your own datums.