@ cr0sh, although there are applications such as animation where a frame buffer would be more suitable, in many cases a frame buffer would not be a good solution. Updates involving relatively few pixels would be slower with a frame buffer. But the main problem is RAM - a 64x128 panels would need 1k, a 64x192 panel 1.5k. Color panels (which will be supported in a future version) would need more RAM then an entire Mega.
That said, the architecture of the Library could accommodate a frame buffer. The drawing and text functions are in a separate layer from the code that sends pixels to the LCD panel. If someone wanted to experiment, have a look at the glcd_Device.cpp module, this could be modified to use a frame buffer instead of LCD memory. But it would be complex to implement and there are more pressing things we are looking at adding in future like:
- supporting more display controller types
- displays larger than 256 pixels
- color displays
But if someone has the desire and skills to implement a frame buffer within the architecture, please do PM me or bill.