Sprite/Entity Screen Wrap

Should my object determine if it should wrap to other side of screen or should the engine determine it?

i think it is a little bit about the design of your sprite and engine.

but it would then be the engine that decides what happens IE collisions rendering etc

but it would proberbly be a better idea to have the engine handle as much as you can give it, rather then handing that control to the object.

just my 5 cents.

i think it is a little bit about the design of your sprite and engine.

but it would then be the engine that decides what happens IE collisions rendering etc

but it would proberbly be a better idea to have the engine handle as much as you can give it, rather then handing that control to the object.

just my 5 cents.

I agree but I am having a hard time passing the information to the wrap function to affect the object that needs to wrap.

I'll assume that "wrapping" means that when an entity leaves one side of the playfield it enters from the opposite side and it is drawn in both places, like the player's ship in Asteroids.
The main differences between putting this behaviour in the entity or in the engine are:

• If the entity is in charge, it has to be able to authoritatively tell the engine that it moved to another point. Allowing only the simulation engine to alter entity positions is better for data integrity.
• If the engine is in charge, it can simply look at entity positions, figure out which ones wrap and where, tell the entity that it moved instantaneously from A to B, and draw the entity (or tell the entity to draw itself to draw itself) both at A and at B.
• If the entity is in charge, it needs all sorts of vague and complicated information from the engine: is it a wrapping level? Should I wrap or move beyond the screen area? In case I have to wrap, where are my wrap borders?
• This complicated information is likely to be accessed and processed repeatedly for multiple entities that wrap themselves, while the game engine can figure it out in advance, maintain a list of entities that are meant to wrap, and check them against shared borders.

I think your better off encapsulating any movement behaviour within the object itself if you want to retain Object Oriented design that is easy to follow (remember you'll probably want to revisit this code at some point in the future).. This isn't a bad thing especially when your learning.

Actually sorry I've made an assumption that your using an OO language and you haven't said this!

Still - put it in the sprite code