GPU drawing and native Ultimate++ controls, with Windows/Vulkan as the current qualified backend. Application code uses GpuRender; it does not manage Vulkan instances, swapchains or command buffers.
The stable local executable is bin/win64/UppVulkanUiDemo.exe. This is the stable whole-UI Release executable. Future qualified builds replace that same file; executables and compiler output are not committed.
The demo opens on Roles & states, with paired dark/light specimens. Choose Olive, Legacy, CineCast, CineWrite, CineFlow or CineStage and switch between Standard, Subtle, Accent and Alert without resetting edits or selection.
- Roles & states: command/icon buttons, selected/disabled states, validation, editable/read-only fields, dropdown, toggle, checks/radio choices, tabs, slider, progress, segmented range and semantic status chips.
- Colour picker / Micro picker / File browser / Text & IME: working control pages.
- Collections: a small tree, table and GPU image.
Run UppVulkanUiDemo.exe --scene-inspector for the animated scene, live inspector,
metric rings, GPU dialog and image/compute menu. The default showcase uses the
Cinespace Roles & states composition and its existing shared theme recipes.
The client area, controls and owned dialogs use Vulkan drawing. The application
retains Windows windowing/input and DirectWrite text services. A compatible
Windows x64 machine needs its graphics driver's Vulkan runtime, not the Vulkan
SDK, U++ or a compiler. The optional --validation mode requires developer layers.
Candidate identity and qualification records the exact executable hash, source/dependency pins and test results. Demo behavior and metric definitions explains what the rings measure.
Add the GpuRender package and include <GpuRender/GpuRender.h>.
| Entry point | Application |
|---|---|
GpuCtrl |
An embedded GPU surface in an ordinary native UI |
GpuWindow |
A custom GPU window |
GpuTopWindow |
A control tree recorded and replayed through a root GPU surface |
Layout, focus, input and control state remain under U++/Ui authority. Compatible presenters share the expensive device/context resources while owning separate surfaces and swapchains. Images, glyphs, vectors and frame queues have explicit bounds; failures in required-GPU mode are reported rather than hidden by fallback.
Usage · Integration · Package map · Examples
For the embedded 3D viewer, use the Ui3DView guide. It covers the control, optional native UI, demo, API, build commands and tested status.
See Windows build instructions. Copy the
GitHubOut.var.example and CLANGx64_Vulkan.bm.example templates into local
configuration and set the dependency/toolchain paths. The qualified Ui revision
is pinned in the candidate manifest; an unrelated Ui working tree is not a
drop-in replacement for that snapshot.
| Directory | Contents |
|---|---|
bin/win64/ |
Latest qualified Windows executables |
build/ |
Disposable outputs, the pinned dependency export and retained local evidence |
render/ |
Public integration and renderer/backend packages |
examples/ |
Control, surface and drawing demos |
tests/ |
Deterministic regression and load packages |
shaders/ |
Shader sources and checked-in generated SPIR-V |
tools/ |
Development utilities |
docs/ |
Guides, qualifications, dependency patches and compressed history |
Windows/Vulkan whole-UI automated qualification covers direct GPU vector/glyph drawing, images, owned dialogs, browser/pickers, complex text and bounded load. The earlier 24 October build passed five-minute tests on both RTX 4070 Ti and SDK-free Iris Xe machines. Its frame pacing/memory results remain versioned evidence; the manifest distinguishes them from tests of the refreshed demo.
Strict whole-UI acceptance remains 8/10 gates (80%), with actual OS IME candidate interaction and physical AA/input/monitor-DPI review recorded separately. The host currently requests system DPI awareness; live per-monitor scaling is not qualified. Release checklist lists the remaining public-release work. Documentation cleanup does not close acceptance gates.
WebGPU, Metal, Linux hosting, asynchronous video streaming and OCIO integration remain later scopes. GPU timestamps and total driver VRAM accounting are not available. Documentation index · Backend roadmap
Apache-2.0; see LICENSE. Runtime distributions must include the applicable dependency notices described in the release checklist.