Hi, yes I read the instructions, their inclusion is appreciated! It is a lot of text though, and having just a short text in the text window to introduce just what one's seeing in the graphical window would make a lot of difference - maybe something like "this does this and that, press any key to start", or "hit the chords before time runs out" in the graphical window - things like that. The same is tor the "Counts" files - they are described in the reference, but it would help if the file dialogue showed a short line describing just what file it wants and on what it's for.
I don't remember just why I tried to load the file, I was just trying around different options to test the stability of the program. Also, for some reason my folder (not the jar archive) was full of files before (I didn't clone the git repo). Now, after deleting all and re-downloading there is only the jar archive and a twidlit.properties file. Not sure what the difference was.
One thing, when choosing the "keystrokes" tutor, it prompts for a file. If you don't give it one, it will give you the alphabet - which is fine, but it wants the alphabet capitalized. Due to how shift works on the twiddler, I would suggest that it would be better to start out without having to worry about the thumb.
I found another bug: In the "chords" tutor, if you press a key combination that has no chord (I tried Win+Alt with the default layout, I have to press it a few times), the program gives a popup "Error: Empty Keypress" and then crashes. I think this may be the relevant part of the traceback:
It's also a bit strange that your own keyboard layout is not remembered between runs - even if I quit the program safely, it's back at the default layout and I have to find my own .cfg file again. If not saving it outright, maybe a "Recent layouts" submenu might be an idea.