Still trying to muddle through. I have a question for you more experienced C++ programmers.
The Python version is implemented procedurally. That is my way of saying, there are multiple loops. In this way, program state (title screen, menus, gameplay, edit mode, etc.) is basically kept in the instruction counter.
It's a comfortable way to program, basically how I would implement things back on the old Commodore 64, but is hard to convert to an event-driven paradigm, which is why the pyglet and, maybe, the C++ versions are bothersome to develop. (Well that and the fact that C++ is maddeningly finicky.) I'm trying to design this one using a master event loop that switches off depending on the program state. Which is not how I ordinarily would do this, but it seems to be what is expected from a more professional program, and when it comes time to make an iOS version would potentially pay off there.
Or will it? I'm making assumptions that might not be borne out by practical considerations. It is an alien way for me to code, a method that requires a bit more forethought than I'm used to. In the past, I've coded in a kind of iterative way: I know generally where I'm going, I think out what will be necessary, then I try to get a bit of the way each time. This seems like something more architectural.
Or is it? Does this make sense to any of you? Is there a better way to do this that I haven't considered?