Hi,
I just wanted to mention that I had issues using this library on a ESP32 project (esp-hal = { version = "=1.0.0-rc.0", features = ["esp32s3", "unstable"] } if the detail are important). I though it might be related to: #27
The example didn't work, and either crashed (silently) the whole board and/or just didn't update the screen. I managed to make it run by taking some inspiration of how kolibri does the buf https://github.com/Yandrik/kolibri/blob/b91fdd88f25c0b684313cdfbcac5399c69eb98c8/src/framebuf.rs#L160-L163
So instead of updating the display with:
display.fill_contiguous(&area, data).unwrap();
I use
match display.fill_contiguous(&rect, fbuf.data.iter().cloned()) {
Ok(a) => (),
Err(err) => log::error!("{:?}", err),
};
and the code seems to behave as expected.
I'm not sure why .iter.cloned is needed, but it fixed the issue and that's good enough for me for now.
Hi,
I just wanted to mention that I had issues using this library on a ESP32 project (
esp-hal = { version = "=1.0.0-rc.0", features = ["esp32s3", "unstable"] }if the detail are important). I though it might be related to: #27The example didn't work, and either crashed (silently) the whole board and/or just didn't update the screen. I managed to make it run by taking some inspiration of how kolibri does the buf https://github.com/Yandrik/kolibri/blob/b91fdd88f25c0b684313cdfbcac5399c69eb98c8/src/framebuf.rs#L160-L163
So instead of updating the display with:
I use
and the code seems to behave as expected.
I'm not sure why .iter.cloned is needed, but it fixed the issue and that's good enough for me for now.