So, I have a routine that does this, obviously, but was one of the early things I worked on and knowing much more, I know there is a better way to do it. I am trying to check the position offset by the potential movement in the next step (stored into temp, let's say) against the edges of the screen (and then if 'beyond' bounds, continue onward, if not, do something else). I have set up some 'bounds' constants, but using BCC and BCS sometimes returns funky results when bounds are set against the edges of the screen (because, of course, the value in temp loops around to the other side of the screen). I'm thinking the best way to do this would be with signed numbers, is that correct?
Again, I have a routine that is functional, but with it I have to play with the bounds values and tend not to be able to make them the screen edges. I've just sort of lazily dealt with it, but now that I'm tightening the bolts quite a bit, I want to fix up things like this. Wondering what you more knowledgeable folks would do for this.
Thanks!
Again, I have a routine that is functional, but with it I have to play with the bounds values and tend not to be able to make them the screen edges. I've just sort of lazily dealt with it, but now that I'm tightening the bolts quite a bit, I want to fix up things like this. Wondering what you more knowledgeable folks would do for this.
Thanks!