Let Blt() do it. Blt already does checking like that to clip your images, so you''re going to end up checking everything twice when you display an image.

Unless of course, your ''objects'' are bigger than one image. If you have some sort of construction that takes 20 blits to draw to the screen, then it might be a good idea to see whether you can eliminate the entire thing before trying to draw any of it.

I guess I should be a little bit more specific too. If you are doing a tile engine, make sure that you are just drawing the range of tiles that have some chance of being onscreen and not running through your entire map and checking each tile. For example, if the upper left corner of the screen is going to be tile (10,10), then there is no need to look at any tiles in the first 10 rows or columns of the map array. Hopefully, what I mean is pretty clear.

Now, if you''re drawing characters and objects too, it depends on how you store their information. For example, if a character is associated with a specific tile of the map, then you can eliminate drawing them along with the tile when the tile is off the screen. However, if you''re using world coordinates to track your objects and players and they aren''t connected to a specific ''square'' of the map, then you will probably have to check each and everyone to decide if it should be drawn.

My original response was referring to things like tiles or objects that are borderline. That is, something that might be JUST off the screen. In this case, just let Blt do the clipping.

I hope I cleared myself up a little.