Philip Howard

They were never supported in the first place- supplying width/height was more a nuisance than a feature since unsupported values would break or be ignored.

Sort of- the buffer size didn't really *do* anything useful. If it's too small you'd get an error, and if it's too large you'd waste RAM. The whole `display.init(buffer)` thing...

Supporting other screens would be nice, but I need: 1. Time 2. The screens to test with Ignoring all the MicroPython veneer over the top, PicoGraphics and the display drivers...

I think the error is on this line: https://github.com/pimoroni/pimoroni-pico/blob/2413713bb8d6e4d6e715b0802d07a2db24c22af4/micropython/modules/badger2040/badger2040.cpp#L182 The `partial_update` is - by default- "blocking" and needs a "false" added here to prevent it from locking up MicroPython.

> Is there a reason I don't get? We have to write C libraries one way or another to support Pico SDK, so it makes sense to bind them as...

Thanks for the encouraging words! And it's not just Pico- still have a whole history of product support nipping at my heels and a certain retro handheld to support. All...

Oh and to respond to @tempusfugit84 (sorry missed out there): > I have a feeling the RGB_keypad will not get much more than it currently has which is a shame,...

Thank you! I'm all for extra features as long as they don't over-complicate things, but this is going to conflict with a pretty huge rewrite of parts of badgerOS so...

Changes are in, though there will be a couple more in v1.18.6. The USER button is now rather difficult to make use of on battery, since pressing any button powers...

Cross-compiling is something of a hassle but the steps to accomplish it are laid out in - https://github.com/pimoroni/pimoroni-pico/blob/v0.3.3/.github/workflows/micropython.yml I've got an open issue reminding me to document this in a...