Skip to content
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

fill() method does not seem to work after first time eink 1.54 display #21

Closed
mrmcwethy opened this issue May 24, 2019 · 5 comments
Closed
Assignees

Comments

@mrmcwethy
Copy link
Collaborator

I have found that I have to start the program over to clear that screen again. A method that works is fill_rect(), but I think that fill() should work too.

testcase.txt

@evaherrada
Copy link
Collaborator

@mrmcwethy Are you referring to the monochrome or tri-color 1.54 eink display?

@mrmcwethy
Copy link
Collaborator Author

I have a metro M4 express with the 1.54 monochrome screen. Also I am using CP 4.0 with latest bundle.

@mrmcwethy
Copy link
Collaborator Author

By the way, I am pretty sure that the mcp_sram.erase(() function is not updating the sram as needed. I change erase to use mcp_sram.write() for each byte and works okay, but slower.

@evaherrada
Copy link
Collaborator

Ok. I'm gonna take a look at this and try to fix it. I'll let you know what I come up with.

@evaherrada evaherrada self-assigned this May 25, 2019
mrmcwethy added a commit to mrmcwethy/Adafruit_CircuitPython_EPD that referenced this issue May 29, 2019
mrmcwethy added a commit to mrmcwethy/Adafruit_CircuitPython_EPD that referenced this issue May 29, 2019
ladyada added a commit that referenced this issue Jun 13, 2019
@mrmcwethy
Copy link
Collaborator Author

This is fixed with release 2.03.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants