You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firstly thanks for taking the time to file an issue. Chances are, you are not the first (and
wont be the last) to have this problem: By creating a public issue, others can browse and
solve their issues - possibly in a self-service style - just by reading the discourse on your
ticket, so try and be clear in the describing the problem you have.
Secondly, github issues are not just for raising problems - if you have a question, a
documentation fix, or suggested improvement, please get in touch.
Lastly, there are a number of related LUMA projects - please check to make sure to create
the issue in the right GitHub repository.
Type of Raspberry Pi
Not all Pi's are equal at the hardware level - what works on one, might not work on the next.
This library has been tested on every variant except the RPi3.
I am not using PI but this issue is not platform related.
Linux Kernel version
Paste in the output from running uname -a at the command line on your Pi.
I am not using Linux but this question is not platform related.
Expected behaviour
Add a few concise notes about what you are expecting to happen.
Even better, if you paste in a code sample that demonstrates what you want to achieve.
If only a small area of the screen got changed, write only that area rather than the entire screen. E.g. find a writeable bounding box of the modified pixels and update just that portion onthe screen.
Actual behaviour
Now add some details about what actually happened - if there is an unexpected crash, paste in the traceback info.
I wrote a small program that updates a numeric field on a SH1106 OLED and it works well (thanks). I did observed though that even ifI change only a small area of the screen, the entire screen is written on each update.
My question is, does Luma support incremental updates? And if not, please add it to your feature request list.
... I found the discussion below but it deals with the rendering side rather than the screen update (i2c in that case). From my experience, the I2C communication is the bottleneck of the screen refresh process with SH1106 in I2C mode.
Type of Raspberry Pi
I am not using PI but this issue is not platform related.
Linux Kernel version
I am not using Linux but this question is not platform related.
Expected behaviour
If only a small area of the screen got changed, write only that area rather than the entire screen. E.g. find a writeable bounding box of the modified pixels and update just that portion onthe screen.
Actual behaviour
I wrote a small program that updates a numeric field on a SH1106 OLED and it works well (thanks). I did observed though that even ifI change only a small area of the screen, the entire screen is written on each update.
My question is, does Luma support incremental updates? And if not, please add it to your feature request list.
My drawing code:
Full program at https://github.com/zapta/i2c_adapter/blob/main/examples/oled_demo.py
The text was updated successfully, but these errors were encountered: