mordv / mnswpr Goto Github PK

I like the idea to keep score. Of course, this implies keeping track of the top times but also measuring the win/lose ratio. I think the minesweeper I used on WinXP when I had no other games would tell me, that I win about 2% of my games.
I would really like to relive that depressing feeling.

As an initial input, I would suggest logging wins, losses, cancelled games and the x top timings for any game. I usually play with custom width/height/mines. So I would hope to keep track of these stats not only for beginner, intermediate and expert but also for my customs games. Maybe store the field size as additional score key.

When I find the time, I will try to dig into how to do this and send a PR for you to refactor.

Keep up the good work!

@felixjulianheitmann
At first, I didn't think it would be possible, but I've found this comment. Turned out you can write commands to stdout to enter and exit fullscreen. I suppose tools like htop or nano use exactly this. Also turned out you can subscribe to stdout resize, so everything works like a charm, really like how it turned out.
Again, thanks for the ideas, for some reason I didn't think about clearing output at all. I have also found persistant library for npm packages, so we might try to track records, PR's are welcome :) Originally posted by @mordv in #3 (comment)

Hi,

I would like to be able to clear my console before start, so I don't have the game at the very bottom of my screen. Also I would like the game to be vertically centered, when using the "fullscreen" option.

I tried implementing that myself, but as far as I could see, the Ink framework does not know about the terminal size. One could set the outermost Box size to the terminal height, but that would need to be updated dynamically when changing the terminal size.

Thank you for the gift to a slightly obsessed Minesweeper enthusiast.

Cheers

I would like to use mouse to play the game. It would be nice to support both keyboard or mourse interaction.

See the following screen recording. Maybe a partial re-render could fix this problems. I do not know whether it is a limit of ink or not.