Closed alex7088 closed 7 years ago
Hello Alex. Thanks for the note. It is not clear to me what you mean with:
8 pixels high dipslay
Do you mean monochrome displays or really a display with the geometry width x 8? I used the driver with a monochrome 128x64 pixel display. What kind of display are you using? Besides that, I think the change you used is safe.
No this is common 128x64 but with original driver it shown only 128x8 Other part of display was off I l send a photo
14 апр 2017 г. 11:21 PM пользователь "robert-hh" notifications@github.com написал:
Hello Alex. Thanks for the note. It is not clear to me what you mean with:
8 pixels high dipslay Do you mean monochrome displays or really a display with the geometry width x 8? I used the driver with a monochrome 128x64 pixel display. What kind of display are you using? Besides that, I think the change you used is safe.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/robert-hh/SH1106/issues/1#issuecomment-294229280, or mute the thread https://github.com/notifications/unsubscribe-auth/AQeEDgycsA3WRRojfV93LaK2oJOiJLiCks5rv9VSgaJpZM4M9zyq .
Found the reason: The underlying class was changed, and the format parameter obsolete for Framebuffer1 was taken stride value. Anyhow, I updated the repository. Thanks a lot.
With Framebuffer1 I can use only 8 pixels high dipslay. When I changes from Framebuffer1 to Framebuffer problem solved