Methods
| Method | Purpose | Notes |
|---|---|---|
createStartUpPageContainer | Create the initial page | Called exactly once at startup. Returns result code. |
rebuildPageContainer | Replace the entire page | Full redraw — all state is lost, brief flicker on hardware. |
textContainerUpgrade | Update text in-place | Faster, flicker-free on hardware. Requires matching containerID + containerName. |
updateImageRawData | Update an image container | No concurrent sends allowed. |
shutDownPageContainer | Exit the app | Pass 0 for immediate exit, 1 for exit confirmation dialog. |
callEvenApp | Generic method call | Escape hatch — all typed methods are wrappers around this. |
Result Codes
For createStartUpPageContainer:
| Code | Meaning |
|---|---|
| 0 | Success |
| 1 | Invalid parameters |
| 2 | Oversize |
| 3 | Out of memory |
rebuildPageContainer, textContainerUpgrade, and shutDownPageContainer return boolean.
updateImageRawData returns a status string: success, imageException, imageSizeInvalid, imageToGray4Failed, or sendFailed.
Best Practices
- Use
textContainerUpgradefor frequent text updates (counters, status, live data) — it avoids the flicker of a full rebuild. - Use
rebuildPageContainerwhen changing the container layout (adding/removing containers, switching between text and list). - Always match
containerIDandcontainerNameexactly when usingtextContainerUpgrade. - Do not call
updateImageRawDataconcurrently — wait for one to complete before sending the next.