feat(debug-ui): add slider editors to the ECS Explorer #977

Closed
opened 2026-10-29 21:22:15 +00:00 by SakulFlee · 1 comment
Owner

Summary

Add slider editors for numeric fields in the ECS Explorer, instead of requiring exact text entry for every value.

Motivation

The ECS Explorer currently exposes editable scalar fields as text inputs. That is precise, but slow for tuning values such as camera near/far, light intensity, transforms, and component parameters. A slider with an optional numeric text field would make inspection and tuning much faster.

Scope

  • Detect editable scalar fields (f32, signed/unsigned integers) and render a slider alongside or instead of the text field.
  • Keep exact text entry available for values that need precise input.
  • Use sensible range/step metadata where the field type or component provides it.
  • Clamp slider values to the field's valid range and preserve existing validation behavior.
  • Support vector fields by exposing one slider per component where practical.
  • Keep ECS edits marking the same dirty flags as the existing text path.
  • Avoid rebuilding the world tree unnecessarily while dragging.

Acceptance criteria

  • Camera near, far, fov, and transform scalars can be adjusted with sliders.
  • Light intensity/range and material scalar fields can be adjusted with sliders.
  • Text input remains available and both paths use the same validation.
  • Slider updates are reflected in the ECS component and realization dirty flags.
  • Widget construction remains testable without a GPU.
  • #971 — debug UI audit
  • #970 — rendering controls panel
## Summary Add slider editors for numeric fields in the ECS Explorer, instead of requiring exact text entry for every value. ## Motivation The ECS Explorer currently exposes editable scalar fields as text inputs. That is precise, but slow for tuning values such as camera near/far, light intensity, transforms, and component parameters. A slider with an optional numeric text field would make inspection and tuning much faster. ## Scope - Detect editable scalar fields (`f32`, signed/unsigned integers) and render a slider alongside or instead of the text field. - Keep exact text entry available for values that need precise input. - Use sensible range/step metadata where the field type or component provides it. - Clamp slider values to the field's valid range and preserve existing validation behavior. - Support vector fields by exposing one slider per component where practical. - Keep ECS edits marking the same dirty flags as the existing text path. - Avoid rebuilding the world tree unnecessarily while dragging. ## Acceptance criteria - Camera `near`, `far`, `fov`, and transform scalars can be adjusted with sliders. - Light intensity/range and material scalar fields can be adjusted with sliders. - Text input remains available and both paths use the same validation. - Slider updates are reflected in the ECS component and realization dirty flags. - Widget construction remains testable without a GPU. ## Related - #971 — debug UI audit - #970 — rendering controls panel
Author
Owner

Implemented in #1017/#1018 and ready for review.

Implemented in #1017/#1018 and ready for review.
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
SakulFlee/Orbital#977
No description provided.