klubhaus/sideline
2
0
Fork 0
forked from genewildish/Mainline
Code Issues 5 Pull Requests Projects 1 Releases Wiki Activity

HUD effect invisible - runs as overlay after display stage #47

New Issue
Closed
opened 2026-03-19 21:46:49 +00:00 by david · 0 comments
david commented 2026-03-19 21:46:49 +00:00
Owner
Copy Link

Description

The HUD effect is positioned as an "overlay" stage, but the overlay logic runs AFTER all regular stages including the display stage. This makes HUD invisible because it runs after the final display output.

Investigation

From engine/pipeline/adapters/effect_plugin.py:

if self.name == "hud":
    return "overlay"  # HUD is overlay stage

From engine/pipeline/controller.py:

  • Overlay stages are applied AFTER regular stages including display
  • HUD runs after display stage, making it invisible

Expected Behavior

HUD should appear on top of the rendered content, before the display stage outputs to the terminal.

Location

  • HUD effect: engine/effects/plugins/hud.py
  • EffectPluginStage adapter: engine/pipeline/adapters/effect_plugin.py (line 32-34)
  • Overlay execution: engine/pipeline/controller.py (lines 793-806)

Solutions

Option 1: Move HUD before display stage in the pipeline execution order
Option 2: Fix the overlay system to run before display
Option 3: Remove HUD from overlay system and make it a regular effect stage that runs before display

Additional Note

There are also multiple overlapping border solutions in the codebase:

  1. Display-level border (BorderMode.SIMPLE) - applied by display backend
  2. Border Effect - applied as pipeline effect
  3. UI Panel (BorderMode.UI) - handled separately

Consider standardizing these as part of the fix.

## Description The HUD effect is positioned as an "overlay" stage, but the overlay logic runs AFTER all regular stages including the display stage. This makes HUD invisible because it runs after the final display output. ## Investigation From `engine/pipeline/adapters/effect_plugin.py`: ```python if self.name == "hud": return "overlay" # HUD is overlay stage ``` From `engine/pipeline/controller.py`: - Overlay stages are applied AFTER regular stages including display - HUD runs after display stage, making it invisible ## Expected Behavior HUD should appear on top of the rendered content, before the display stage outputs to the terminal. ## Location - HUD effect: `engine/effects/plugins/hud.py` - EffectPluginStage adapter: `engine/pipeline/adapters/effect_plugin.py` (line 32-34) - Overlay execution: `engine/pipeline/controller.py` (lines 793-806) ## Solutions Option 1: Move HUD before display stage in the pipeline execution order Option 2: Fix the overlay system to run before display Option 3: Remove HUD from overlay system and make it a regular effect stage that runs before display ## Additional Note There are also multiple overlapping border solutions in the codebase: 1. Display-level border (BorderMode.SIMPLE) - applied by display backend 2. Border Effect - applied as pipeline effect 3. UI Panel (BorderMode.UI) - handled separately Consider standardizing these as part of the fix.
david closed this issue 2026-03-20 08:04:15 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
epic:#2
epic:#20
epic:#3
epic:#4
epic:#5
epic:#6
epic:Data Source
epic:Display Backend
epic:Display Tools
epic:Effects
epic:Pipeline Architecture
epic:Sensors
status:feature-complete
status:in-progress
status:released
status:tested
type:epic
type:epic
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
david genewildish
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: klubhaus/sideline#47
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?