dwt/notes/GUI_APPS.md documents text, GC and fill calls but has no XImage entries, so a client cannot create or upload a bitmap without guessing addresses. The ROM itself warns about format handling:
XPutImage: bits_per_pixel conversion unimplemented. at bit 0x3F9D0E80
XGetImage: Can't get requested memory at bit 0x3FD567A0
(see reference/rom-strings.txt).
The termtris port avoids images entirely (XFillRectangle/XDrawString), so this path is untested in the tree. A real client needs a 1-bit XImage (XYBitmap, LSBFirst) and there is no documented entry point or format contract.
Requested: extract and validate the XCreateImage, XPutImage, XDestroyImage and (optional) XGetImage entry points, and document the supported format: depth, format, byte_order, bitmap_unit, bitmap_bit_order, bitmap_pad, bytes_per_line. A minimal xshow-style probe (create a 1-bit image, XPutImage, capture VRAM) would pin the layout and the bits-per-pixel limitation.
`dwt/notes/GUI_APPS.md` documents text, GC and fill calls but has no `XImage` entries, so a client cannot create or upload a bitmap without guessing addresses. The ROM itself warns about format handling:
- `XPutImage: bits_per_pixel conversion unimplemented.` at bit `0x3F9D0E80`
- `XGetImage: Can't get requested memory` at bit `0x3FD567A0`
(see `reference/rom-strings.txt`).
The `termtris` port avoids images entirely (`XFillRectangle`/`XDrawString`), so this path is untested in the tree. A real client needs a 1-bit `XImage` (XYBitmap, LSBFirst) and there is no documented entry point or format contract.
Requested: extract and validate the `XCreateImage`, `XPutImage`, `XDestroyImage` and (optional) `XGetImage` entry points, and document the supported format: depth, `format`, `byte_order`, `bitmap_unit`, `bitmap_bit_order`, `bitmap_pad`, `bytes_per_line`. A minimal `xshow`-style probe (create a 1-bit image, `XPutImage`, capture VRAM) would pin the layout and the bits-per-pixel limitation.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
dwt/notes/GUI_APPS.mddocuments text, GC and fill calls but has noXImageentries, so a client cannot create or upload a bitmap without guessing addresses. The ROM itself warns about format handling:XPutImage: bits_per_pixel conversion unimplemented.at bit0x3F9D0E80XGetImage: Can't get requested memoryat bit0x3FD567A0(see
reference/rom-strings.txt).The
termtrisport avoids images entirely (XFillRectangle/XDrawString), so this path is untested in the tree. A real client needs a 1-bitXImage(XYBitmap, LSBFirst) and there is no documented entry point or format contract.Requested: extract and validate the
XCreateImage,XPutImage,XDestroyImageand (optional)XGetImageentry points, and document the supported format: depth,format,byte_order,bitmap_unit,bitmap_bit_order,bitmap_pad,bytes_per_line. A minimalxshow-style probe (create a 1-bit image,XPutImage, capture VRAM) would pin the layout and the bits-per-pixel limitation.