Wouldn't that depend on what else is happening?
Ideally 'frame' would be a field within an 'explosion' object.
If you set 'frame' as global to the whole program and you have, say, 10 explosions, you'd need 10 seperate global statements which is cumbersome and, most likely, unworkable.
Ideally 'frame' would be a field within an 'explosion' object.
If you set 'frame' as global to the whole program and you have, say, 10 explosions, you'd need 10 seperate global statements which is cumbersome and, most likely, unworkable.
which is why now I have moved everything back into a type, and created various functions for various explosions. a missile impact, a ship blowing up etc etc...
also I believe the reason I started this thread was because I HAD put the local frame outside the if statemment at one point to see if that helped and it didn't make a difference. I think. Ill do it again when I leave work and let you know for sure. Regardless I thought it was weird hence why I posted, since I am sure that I had it outside that scope, maybe not in the example I posted, but I did try it like that to see if it had solved the problem.
as for posting more code, thats it basically... thats the function and the function was in the loop and when you got HIT, the boolean hit became true and started the block, and it works when frame was a global.
thanks again