I don't know how I overlooked this, but this is really cool!

i like the sweeping effect.  although it could hurt highscore times...

i like the sweeping effect.  although it could hurt highscore times...

If it does the timing separately, the sweep would pause the clock for just that moment, and that'd be perfect, though.

Noticed that too. And how can there be a 1 in a corner with blank squares surrounding it?

The game looks great, though

About the slowness at the bottom left: it's a bit complicated, but it's also something that's inherent in the design.  If I manage to find a method to make the program sweep back and forth vs from just one side, it should be much improved.  

Also, the one in the corner?  Are you referring to the upper left one?  I'm pretty sure it was touching a mine...

Also, how would I do time?  I've been looking through my list of commands, and I can't find any timer-related commands.  Or am I just being stupid and overlooking it?

To prevent any delays, could I use interrupts?  Create a subprogram that adds 1 to a variable each time, and after x amount, I display another second?  I think this might be also compatible with older calculators, even though the seconds might be more elongated on the older ones.  Hmm.  If I've misunderstood what an interrupt is, this'll all go out the window...

Edit: 20th post!

How exactly are you doing the checking for the bubbles? You could maybe make a routine that checks up and then below the selected point and then just travels one way and then back, if that makes sense. I can't better type that out if you need. Just a thought though.

As for time, technically the only way you could do accurate time would be by using assembly code with 84+'s (and I think 83+SE's can but they don't have it built in, just something but I don't know.) but Axe has no timer features that I know of. I think though the closest you can get is by using pseudo timing.

that's pretty sweet!
unless you find some way to radically increase the speed of the sweeping, though, i'd leave it as it is. pausing screen update would ruin the gray, and the only other way i can think of doing it would be storing the data in a different spot and then copying it all over after the sweeping process is over(which adds a bit of unnecessary code). oh, and a suggestion: you should try making scrolling maps larger than the screen, as nobody has ever done that either, and it would make your sweeping effect more useful. good luck!