-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Fast Mode" and clearing #7
Comments
I think the key thing here is that both
The purpose of the Because This concept is not made particularly clear, and I will need to look into re-writing the doc to highlight the true purpose of You may find it useful to reference the code snippet given in the API: #include <heltec-eink-modules.h>
DEPG0150BNS810 display(2, 4, 5);
void setup() {
display.clear();
// Begin fastmode
display.fastmodeOn();
DRAW (display) {
display.setCursor(10, 10);
display.print("ON");
}
delay(2000);
DRAW (display) {
display.setCursor(10, 10);
display.print("still ON");
}
delay(2000);
// Back to normal drawing
display.fastmodeOff();
display.setWindow(0, 40, 100, 100);
DRAW (display) {
display.setCursor(10, 40);
display.print("OFF now..");
}
}
void loop() {} Note that if you are 100% certain your display is blank, you do not need to call
Note that with Mega2560 and DEPG0150BNS810, there is sufficient RAM that paging is not used by default. If you choose not to enable paging, you are also free to use the alternate syntax outlined in API: update(), and the update.ino example. Hopefully this helps point you in the right direction. Please let me know if I have misunderstood the problem. |
Thanks for the reply! I'll try out the approach described soon. |
I have a Heltec 1.54" V2 (BW) that seems to work properly with the
fonts
example ifDEPG0150BNS810
is defined on an Arduino Mega 2560. But for some reasonfastmodeOn
seems to have the exact opposite effect. Meaning for a proper full clear I have to do:Then the display clears the entire contents without ghosting.
clear()
?So the resulting minimal working code looks like this:
If I merge the two
DRAW
s in the loop text starts overlapping (seems to do a partial update only). If I don't dofastmodeOn()
in the firstDRAW
there's always slight ghosting. If I don't dofastmodeOff()
in the second block, it displays the previous value and then (with ghosting) the new value on a previously fully cleared display.What I'm getting at is that I'd expect this to work (draw the new text once in a while without ghosting), but it doesn't:
What wrong assumptions am I making about the display or the library?
The text was updated successfully, but these errors were encountered: