Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Add custom menu - to add custom grids #10
Fix: add a negative sign if the number of bombs placed are greater than then number existing Fix: minesweeper.png to better display positive and negative signs Fix: display of negative signs Formatting Fix: to use String.toList formatting
WIP: add fields for custom grid types WIP: add custom menu types, working through the compiler errors WIP: trying to display the custom menu WIP: trying to work out why it is not working!?! WIP: displaying all the input fields
I suspect the problem might lie somewhere here:
(TBH there is still much I don't understand when attempting to read the code. ) I might have a closer look at the Grid.floodcells method tomz.
in terms of defining the general goal for this menu, here's a nice screenshot:
in this menu, you can click the radio buttons to switch between options, but then you have to click "ok" to confirm. you could also "cancel" to just close the menu and forget about it.
when you open the menu, the current level is pre-selected for you. this kinda works in Elm, but currently, it doesn't pre-select anything if you're on
can we aim for all this? does anything seem unattainable?
I have added the above defaults in windows: 9 * 9 * 10.
The rest is just adding the text / labels + css.
The is a performance problem somewhere, so when large numbers are added and the bomb count is low, my browser basically crashes. can easily added support for large numbers though.
Question re: deubbing:
can be done, more or less. it's just a matter of css, and i gotta have a look at that performance issue.
pls LMK your thoughts.
i guess i like opening the door to supporting other settings. in general, settings menus tend to have ok/cancel buttons as an explicit step to dismiss the menu. i also think it'll simplify some code, since we'll be dispatching the same
it doesn't look very smooth right now when the inputs jump in. disabling the input, instead of removing them, when a non-custom difficulty is selected will make this less jarring. (i think it'll also make some of this code more straight-forward
i can help with the styles once all the functionality is settled. i have an idea of how this code might look, but i don't want to rob you of figuring it out lol. let me know if i should explain further