Registry API

The registry module exposes RegistryProxy, a small wrapper around the native global registry. Most application code should use scenes.select_scene(); registry.registry.current_scene_name remains available for compatibility and direct low-level control.

Public Surface

Surface	How to use it	Why it exists
registry.registry	Import it from tuix.core.registry and access properties on it.	Provides a Python proxy over native registry state.
registry.registry.current_scene_name	Read or assign bytes/str scene names; prefer scenes.select_scene(name) for normal switching.	Maintains compatibility with older code and fallback paths that set the active scene directly.

Advanced Mirrored Fields

When native registry state is available, RegistryProxy may mirror scenes, subcycles, builders, frame_counter, next_uid, terminal_width, terminal_height, terminal_width_old, terminal_height_old, and debug_config. Treat these as diagnostics unless you are debugging the engine.

Usage

from tuix.core import registry, scenes

scenes.select_scene('Main')
active = registry.registry.current_scene_name

# Compatibility path:
registry.registry.current_scene_name = 'Main'

Prefer Scene APIsDo not mutate mirrored low-level fields directly in application code. Use scenes, buffers, objects, and engine helpers instead.