WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Conversation

@mungewell
Copy link

I have a project with multiple modules, when 'blink()' was enabled they blinked a slightly different rates... which looked funky.

The register for blinking also includes a 'display_on' bit, so I access that with a vaule of '-1' to turn off the display(s). Set a normal blink rate to turn display(s) back on.

Tested on the 'HT16K33Segment' from Adafruit.

I have a project with multiple modules, when 'blink()' was enabled
they blinked a slightly different rates... which looked funky.

The register for blinking also includes a 'display_on' bit, so I
access that with a vaule of '-1' to turn off the display(s). Set a
normal blink rate to turn display(s) back on.

Tested on the 'HT16K33Segment' from Adafruit.
@mungewell
Copy link
Author

I realized that it would be more useful if repeated writes of '-1' toggled the display off, on, off, on. That way the app wouldn't need to track the state.

I'll revise the patch tonight...

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

Successfully merging this pull request may close these issues.

1 participant