Hello,
I'm after some advice on the following design idea. I'm currently
creating some classes for my new side scrolling shooter game (R-Type
style). The background elements (roof and floor items) are individual
sprites which are moved from right to left. My idea is to create a pool
of these sprites and hold them in a list. When a background sprite is
needed I get one from the list and set its visible flag and x,y
coordinates. Each update its X position is decremented until it
disappears off the left hand side of the screen. Its visible flag is
then set to false so that its available again. If all the background
sprites are in use I'll create a new one and add it to the list. Does
this concept sound reasonable ? The only downside that springs to mind
is the code that will need to traverse the list to find a background
sprite that isn't being used. As the background sprites are the same
size the list would only need to be checked once every 32 frames
(assuming that the sprite is 32 pixels wide and scrolled 1 pixel every
frame).
Any comments ?
Ian
This email is intended solely for the person to whom it is addressed and may contain confidential or legally privileged information. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. Please notify the author by replying to this email and destroying all copies of the email and attachments. Access to this email by anyone else is unauthorised.
Email may be susceptible to data corruption, interception, unauthorised amendment, viruses and delays or the consequences thereof. Any views or opinions presented are solely those of the author and do not necessarily represent those of Grosvenor Technology Ltd.
Grosvenor Technology Ltd. (incorp. Newmark Technology Ltd.) is a company registered in England with company number 2412554.
The Grosvenor Technology Ltd. Registered Office address is Millars Three, Southmill Road, Bishop's Stortford, Herts, CM23
[Non-text portions of this message have been removed]
.
