Damn inspiration strikes again This is a small side project i have been working on, i whipped up this code in a few hours, and its already showing some promise!  Its just a small and fun arcade game called Xonix.  There are several balls bouncing around the arena.  You can move your cursor to create walls to lock in the balls into smaller containers.  But if a ball hits a wall while its being constructed, it will start to disintegrate, and if the wall disintegrates all the way to your cursor before you reach the safety of land, you lose a life.

For those interested, i had to write a flood filling algorithm in order to get the filling to work properly.  I use a special scanline filling algorithm which i have to admit is quite shiny I think ill post a demo of the filler in the Axe Algorithm thread later...

Also note that this is only a side project and does not take precedence over other Projects like PortalX This isnt actually currently being worked on, i just felt like posting what i had.

Ah, this looks similar to <a href="http://en.wikipedia.org/wiki/Jezzball">Jezzball </a> that was packaged with older versions of windows.  It looks very well implemented so far.

Nice! I hope this gets finished.

That is very cool. Great job on it

Do I see grayscale in the game? o.o

This looks cool!  I made this game before on the computer, its really addicting.  I'm also curious how you did the fill algorithm since there are 2 or more sides to every line and you have to detect if you've trapped anything in either one.

the game looks great(that is totally an improvement over impossible jezzball), but im more excited for that filling algorithm. if you dont post it quickly i might have to try writing a slightly less shiny one just so i have it when it will inevitably be needed in some future prog. nice work!

Just wondering, what happens if you trap a ball in a spot that gets filled in?

Thats the beauty, any side that contains a ball wont be filled in Unfortunately when i tried to port the filling algorithm from tilemap to screen coordinates, i ran into a problem.  All the things that make this routine fast are not applicable on the graph screen, since you would need to go pixel by pixel anyway.  With this right now, since i have a buffer for the screen, i dont have to do bitmasking for every pixel (via a pixeltest or a pixelOn) But if i transfer it over to the graph screen, its just as slow as every normal filling algorithm I'll write a general routine anyway soon and upload it tho, since it can be useful.

As for how the logic works in this game, once a wall is completed, every BALL flood-fills its area, marking it with a number.  Anything that has been marked is kept clean, and anything not marked is set as solid.