Render Intelligent-only components; fonts follow the display direction

- SLText, TextSelect, DataRecord, FileBrowser pixel-exact against the Intelligent simulator;
  ComboBox and Switch with approximate anti-aliased edges; media/file components draw nothing
- fonts: header byte 3 = 0x0A + direction, glyphs in the direction's pixel order, Intelligent
  glyph data 4-byte aligned -- reproduces the Editor's own font conversion byte for byte
- Intelligent 3D frames: left edge drawn over the bottom edge

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
mangavalkandClaude Opus 5.5 committed 2026-11-16 00:26:27 +01:00
1 parent 56062e1a3e
commit 49fee337d7
10 files changed
+334 -32

No files matched your search

+1 -1
View File
@@ -44,6 +44,6 @@ Back up the user's file first (copy it) unless they said not to; edits write in
- Writes projects for Nextion Editor 1.68.2; the user still compiles/uploads the `.tft` with the
Editor (or Nexus for uploading). nxhmi cannot compile `.tft` files yet.
- Rendering: Intelligent-only components are not drawn yet.
- Rendering: Intelligent-only components are drawn as in the simulator (ComboBox and Switch edges are approximate). Run-time content (files, records, video) is not drawn. Fonts and pictures are stored in the project's display direction; `add_font`/`add_picture` handle it.
- QR codes on Basic displays: long texts can exceed the display RAM; the Editor then refuses to
compile ("not enough memory ... QR code"). Keep QR texts short there and compile to check.