Steps to reproduce:

1) Go to Config menu and hit "Activate Classic Mode" (relevant checkboxes will be disabled)
2) Click Apply, OK
3) Exit the Config menu
4) Re-enter the Config menu

The checkboxes are enabled again.

Tetris

So, I already made a Tetris clone a while back written in Python and very loosely following a tutorial which I ended up not liking very much.

The project is finished and playable, but unfortunately I'm having problems with trying to get it to build as an executable file. There are also many bugs in the game which I haven't yet ironed out, and a few features (each tetrimino block having its own colour, hold feature, t-spin physics and sliding rotation physics) that I haven't quite managed to get right, although I have made a start.

If I can at least figure out how to make the .exe (followed a tutorial but it didn't work), I'll upload what I have so far.

Ideally, though, I'd like to see if I can find a better tutorial and start from scratch. I find Python/PyCharm/PyGame very unintuitive and fiddly to work with. Things like not getting an executable straight from the Build/Debug process just seems a bit rubbish tbh. But, I keep hearing that Python is meant to be one of the best languages to learn, so, I guess I'll persevere with it.

EDIT: Here's the .exe (which doesn't work for me, maybe it will work for you?) and the Python file, which will run if you have Python installed on your PC.

Pong!

I've written this one in Delphi; It's my first project to be completely made from scratch!

I followed this tutorial, which is actually for Lazarus (although both use Pascal as their base language, so almost all of it is identical).

The tutorial was excellent; the presenter makes numerous mistakes throughout the video, but rather than editing these out, he takes the time to explain the mistakes and of course correct them as he goes along. I found this to be a valuable learning experience, and have added a few shortcuts to my Delphi toolbox (such as Ctrl+Shift+C to auto-create procedure code from the declaration).

Anyways, enjoy Pong! It's controlled using the mouse.

I want to post an enumerated list. Instead of 1), 2), 3) as you did, I write 102), 101), 100), 99). Nobody bats an eye because these numbers are very useful.

RR looks like this to me:

1, 2, 3, 4, 5, 6, 7, 8, 9 ... 99, with the lowest number meaning "lems come out slowly" and the highest number meaning "lems come out quickly." This makes sense, works as I need it to in-game, and no further information is required.

SI, on the other hand, looks like this:

107, 106, 105, 104 ... 4, with the highest number meaning "lems come out slowly" and the lowest number meaning "lems come out quickly." OK so far, I guess, but now I need more information ... why is the lowest number 4? Why does it stop at 4 and not go all the way to 1? Why does it start at 107? These are questions that, as a player, I am bound to ask whether I've seen a Lemmings game before or not.

So, maybe I take the time to find out that it's the number of pixels between lemmings. OK, I understand it a bit more now but... is the game really going to expect me to know about pixel distance between lemmings? As a casual player, that's a bit of a red flag!

1 - 99 is intuitive and simple; I can see that, when the number is higher, the lems come out faster. A scale going from 107 - 4 makes far less intuitive sense to me personally, even when I know what it means. I don't care about the exact pixel distance between the lems, I only care how it translates to what's actually happening on screen, and I can find out by playing the game what sort of figures are useful.

New keyboards will be produced. Instead of the "1" key, they have a "102" key. If we don't want the two extra digits when we type, we can erase them afterwards every time. I'll buy this keyboard, I think that keyboard is as useful as the ones we have. 102 is a natural figure to type often; after all, most people start counting from here.

Heh, good way of illustrating your point But, I don't actually agree that RR presents this sort of problem. "Low is slow, high is fast" is all the player needs to know, and wherever exact figures come into play, "RR75" means just as much as "SI28" if what you're seeing on screen is the same result.

you make a symbol for fast and a symbol for slow, then you don't have to swap them

Yes, great idea. UP and DOWN arrows could work, or maybe a single right-facing arrow for "slow" and 3 stacked right-facing arrows for "fast"; I'll see about making a split button with the number displayed in the centre. That way, continuing to support both RR and SI should be easy enough even without graphic-swapping. That solves the third issue.

If the votes remain as they are, I'll likely keep the option and not try to crowbar it into Classic Mode. That way, I can forget about it, those who want to use it can do so, and the Config menu is kept relatively clean and tidy.

Yeah, this is something I can look at adding, for sure.

I'd need some help with it, code-wise. Although the changes I've made to SLX so far might make it look like I'm capable enough of doing pretty much anything, a lot of it has only involved tweaking existing code (or adding old removed code back in). Writing in brand new features is still a little bit beyond me.

I am enjoying learning, though! Plus, the more features I successfully implement, the more I'll want to continue adding in other stuff that people want, so... watch this space

---

Thinking about this some more, what do people think of the idea of having more picture/animation-based sound cues (rather than words), in order to further optimise the accessibility potential? Here's an example:

Re-fixed in 500e6efe8 using the same code from the NL fix.

Thanks for the explanation namida, helps to know exactly what was going wrong there.

In fairness to Dullstar, his fix has helped me to learn a lot, so it's all good

Working notes.

The new panel code will have to look something like this:

New function "ScaleFactor"

If window/screen <= 450, ScaleFactor = 1
If window/screen <= 900, ScaleFactor = 2
If window/screen <= 1350, ScaleFactor = 3

For ScaleFactor = 1, use panel450.png
For ScaleFactor = 2, use panel900.png
For ScaleFactor = 3, use panel1350.png

(each panel graphic will have the icons pre-drawn onto the graphic itself rather than overlayed; there will be an unused blank button graphic in gfx/panel to help users with designing their own buttons)

procedure DrawPanel;

Step 1: Lay down the panel.png
Step 2: Draw the correct skill icons
Step 3: Make clickable areas
Step 4: Assign functions to the clickable areas
Step 5: Draw the minimap
Step 6: (use existing Minimap code for functionality)

(All code for drawing the panel will be multiplied by the ScaleFactor)

---

(To further add to the confusion, I'm looking at getting RR/SI onto one button; if this proves too difficult/not worth it, then it will remain as 2 buttons)

Then, there will need to be code to multiply the (correct) panel if the screen is a certain size; not sure exactly how to do that yet but there probably is a magic formula for the purpose, maybe even in the existing code