You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, text output is the major focus of the module.
For simple graphics and effects, it should be possible to set/clear individual pixels (or rectangles), or toggle them.
The latter functionality would require to keep an image of the display in memory, I think.
Having a bit pattern in memory would also provide support for scrolling (issue #3) and what I think "oscillation" (issue #4) means...
The text was updated successfully, but these errors were encountered:
IMHO it's an extension of #1. Adding a require("bit") seems unavoidable in the long run (and. e.g. reverseBytes would profit from bit operations, saving several K of heap space).
Currently, text output is the major focus of the module.
For simple graphics and effects, it should be possible to set/clear individual pixels (or rectangles), or toggle them.
The latter functionality would require to keep an image of the display in memory, I think.
Having a bit pattern in memory would also provide support for scrolling (issue #3) and what I think "oscillation" (issue #4) means...
The text was updated successfully, but these errors were encountered: