-
Notifications
You must be signed in to change notification settings - Fork 27
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
Questions while trying to use epd-waveshare instead of il3820 #14
Comments
To mimich the ELM architecture. Also to allocate only when needed, and to not depend on stm32 types without generics everywhere. I quite like that the buffer is completely decoupled from the driver. I begun the il3820 crate before you publish your, and I never take the time to polish it for publication. Now, the size of the display is quite hard coded in the rendering, some work need to be done if we want to use different screen size. |
Do you plan to construct a clock? I'd be interested by photos, even just on a breadboard! |
Yes, I am trying to use your clock here :-D |
I see you've done a lot of refactor to your driver. One time you publish 0.3 on crates.io, I'll happily accept a PR using your library that looks much better than mine. Any news on the photos of your project? |
I'm hanging on a bug where it doesn't set the fast refresh rate once more after the slow full refresh at the full hour. As soon as it's completly working I am happy to publish ;-) |
If you have any more photos, I'll happily add them to the gallery. |
I tried to use my epd_waveshare crate for this app instead of the il3820 which is basically just a slightly different driver for the same display. (the epd-crate also includes 2 other epds).
The biggest problem I have right now is that ui:view always creates a new buffer/display_ribbon_left. Is there a reason for this? (https://github.com/TeXitoi/rusty-clock/blob/master/portable/src/ui/mod.rs#L152)
The text was updated successfully, but these errors were encountered: