More DungeonView

Hello, loves! If there was a feature I wanted, I’d do that. There isn’t, so we’ll look for some more small but significant improvements. Fiddling while Rome burns? Why not? In a Mastodon exchange involving flying monkeys ( my pretties!) @GeePawHill subtly suggested that if my DungeonView is too hard to test, I might be “doing it wrong”, and that perhaps it’s doing things that actually belong in the model, Dungeon, et al. He challenged me to think of something that clearly should not be in the model but that requires logic. We’ll keep an eye out for that. Mostly, however, we’re just here to try to carve DungeonView up into smaller chunks, so as to make it easier to understand and to work with. Along the way we’ll keep an eye out for “logic”, conditional or looping code that might suggest something. One thing comes immediately to mind as soon as I open the class: it has about seventy-leben lines of setup code. Let’s start by looking at that. It seems likely that a lot of that might be…