I've seen several PRs use the internal array sizes of Framebuffer to work out the width/height, and really that should be done through the abstract interface incase we ever want to change how the pixels are stored. This is a bit of an oversight in the Claudius API as the information in available on the Screen.t to the tick function, but that's not necessarily true in other places!
I've seen several PRs use the internal array sizes of Framebuffer to work out the width/height, and really that should be done through the abstract interface incase we ever want to change how the pixels are stored. This is a bit of an oversight in the Claudius API as the information in available on the Screen.t to the
tickfunction, but that's not necessarily true in other places!