thanks guys.
@Enay - good idea, this seems to be kinda what Curtastic's code does, so definitely worth looking at using arrays.
@Tony - thanks for this, this is loads quicker than mine! (I just need to work through the code to get my head around it).
@Curtastic - thanks for your code. I do think it is a little easier to understand initially (even though I don't know BB at all). It seems to be a little similar to my code in essence, except you track each pixel you check in an array, so that it only gets read once, whereas in mine each pixel could potentially be read several times - obviously slowing things down a lot. Be interesting to see it converted into blitzmax to compare.
Thanks chaps - big help as always
@Enay - good idea, this seems to be kinda what Curtastic's code does, so definitely worth looking at using arrays.
@Tony - thanks for this, this is loads quicker than mine! (I just need to work through the code to get my head around it).
@Curtastic - thanks for your code. I do think it is a little easier to understand initially (even though I don't know BB at all). It seems to be a little similar to my code in essence, except you track each pixel you check in an array, so that it only gets read once, whereas in mine each pixel could potentially be read several times - obviously slowing things down a lot. Be interesting to see it converted into blitzmax to compare.
Thanks chaps - big help as always