SixelPresentationSupport

Namespace: Hex1b.Sixel

Assembly: Hex1b.dll

Describes how the effective upstream presentation can render Sixel graphics.

public enum SixelPresentationSupport

Fields

Headless

There is no real display; Hex1bTerminal's own authoritative screen/graphics model is the sole source of truth (for example headless test harnesses).

Returns: SixelPresentationSupport

Headless = 3

Native

The upstream terminal understands the Sixel protocol natively and Hex1b's Sixel DCS bytes reach it unmodified (raw passthrough).

Returns: SixelPresentationSupport

Native = 2

None

Discovery (or a direct declaration) affirmatively concluded that the effective presentation cannot render Sixel graphics. Workloads must not be told Sixel is available. Distinct from — this is a confirmed negative answer, not an absence of an answer.

Returns: SixelPresentationSupport

None = 1

Unknown

Whether the effective presentation can render Sixel graphics has not been established: discovery has not run yet, has not concluded, or a probe timed out or returned a reply that could not be parsed. Workloads must not be told Sixel is available, but this is distinct from — nothing has been confirmed either way.

Returns: SixelPresentationSupport

Unknown = 0

Remarks

This is deliberately separate from Hex1b's own parser/model support for the Sixel protocol (which is unconditional — Hex1b always understands and models Sixel DCS sequences regardless of what sits downstream). instead answers whether the effective presentation renders Sixel natively or maintains an authoritative headless model. That is a property of the effective presentation path, discovered by #455.

and are deliberately distinct values, not a single collapsed "no support" state: means discovery has not run, has not concluded, or could not reach a confident answer (for example a probe that timed out or returned a malformed reply); means discovery (or a direct declaration) affirmatively concluded the effective presentation cannot render Sixel. Workload-facing feature reporting (for example SixelNode deciding whether to advertise Sixel to a hosted app) must treat both and as "do not advertise" — never assume support, and never silently substitute a specific cell size when support itself is unknown — but code that needs to tell "never checked" apart from "checked and no" (for example diagnostics or a support-status display) can rely on this enum alone, without also inspecting .

is the type's default value (numeric 0), so a instance nobody has explicitly configured reads as "unknown," never as "confirmed unsupported."