Wow! 2.0 was a long time ago! I think in 2.1, I made some the change to the way the minefield generation works.
To make a long story short, one of the features I incorporated was that no mine can be present in any cell surrounding initial click. In essence, the cell you click will always be a zero. This is how Microsoft’s version works as well. If you set up the minefield prior to clicking, you need to do some checks on initial click and move mines around. By waiting for the user to click, it ensures we can do the minefield generation all in one go, which is just a bit simpler. Re: the Flag. I’ve gone back and forth on it. Myself and a few others were having trouble distinguishing an ASCII character from the surrounding numbers at a quick glance. Personally I found the checkerboard a bit more readable. Better yet would be an inverted ASCII but I haven’t managed to work on that yet. Make sure to check out what happens when you click a number cell, and it has the appropriate number of flags around it. -George On Tue, Feb 14, 2023 at 9:22 PM B 9 <[email protected]> wrote: > Just note, I already put together a 2.3.1 release, which significantly >> increases cursor responsiveness. Try it out if you have time. > > Works great on my Model 200 once I commented out line 3010. (Until I hit > the 'H' key, anyhow). > > I like that you are using asterisks ✳ for the mines now. That makes more > sense to me than capital "M"s. > > I did find the new flag character (checkerboard, 🮕) confusing, but maybe > I'll get used to it. I think I'd prefer something that looks more like the > official minesweeper flag. Perhaps a capital 'P' or a question mark? Either > of those would also have the benefit of being ASCII text, so TSWEEP would > be portable to the international "Model T"s by Kyocera, Olivetti, and NEC. > > Out of curiosity, why can the user now move the cursor and pick a square > before the mines are placed? > > —b9 > > > >
