Going Touchscreen means I can skip range checking, Dpad, Cursor. Coupled with a little change in Data Structure means I can save enough to fit the code in one screen. There's a little space. Maybe a cursor sprite?
MineSweeper version 2. Now with Touchscreen! Sorry, but you need to calibrate TX,TY manually. Difficulty Level is D. I can barely squeeze this into one screen. But I did. :)
Turns out, there exist a version of minesweeper in one screen. I had to take certain shortcuts, though, so the game play suffers somewhat. I'll post it out there.
Playing Coding Golf, the least amount of keystroke of a given program, can be fun. However, I still prefer clean algorithm to outright compression. I wonder if I will ever write significant sized program. All my programs so far has yet to break 100 lines, where as I see others clocked in at hundreds of lines!
Here's the rest of @LOSE subroutine. I need a @WIN sub, as well. This needs more obvious presence, but I was too tired, and can't come up with a good idea. Please suggest some to me, and I'll see if I can put it in action. 2+ of 2. ^_^;
Oops. Sorry. It's a little over 2 screens. I realized that I needed a much more significant losing show than just the word "BOOM", so now it's a little over 2 screens. It used to fit just so.
You can start by reading code other people have written. I tend to write One Screen Code challenge to help people. Then you look up documentation to see what each command does, and try to understand the program. HTH.
A little inaccuracy. That DIM CC[1] should be DIM CC[0]. I was unsure about whether or not I can define an array with zero length. Turns out I can. Oh, well. Learn something new everyday! :)
Here's another example on how you can use it: String compression! I added a decompression routine using Ed's tip on array length using LEN. Thanks, Ed!