Interface trait is too limited

[ost-ing]

Hello,

The Interface trait doesn't really allow much flexibility with custom strategies, or experimentation, for example its hard to know the pixel position that would be written (without extracting this from the send_command function).

In other display implementations, there is an additional layer for custom caching and optimization strategies, for example the ssd1306 https://github.com/rust-embedded-community/ssd1306 has a BufferedGraphics Mode.

I'm interested in implementing some kind of Dirty Rectangle method for selective clearing of the screen, because at the moment clearing the entire screen on an stm32f4 at 42MHz, greatly reduces the FPS and introduces flicker.

[rfuest]

The Interface trait is the wrong layer of abstraction for what you are trying to implement. You can uses something like a embedded-graphics Framebuffer to prepare a larger buffer, which you can then send as one update to the display.