Skip to content

Comments

Disable propulsion controls while docking#2723

Open
oznogon wants to merge 6 commits intodaid:masterfrom
oznogon:gui-controls-logic-docking
Open

Disable propulsion controls while docking#2723
oznogon wants to merge 6 commits intodaid:masterfrom
oznogon:gui-controls-logic-docking

Conversation

@oznogon
Copy link
Contributor

@oznogon oznogon commented Feb 17, 2026

Stacked on #2720.

If a ship has a docking port, disable sliders on warp, impulse, and combat maneuver controls, and the Jump button on jump controls, while docking or docked. Re-enable them when undocked. This reduces the ambiguity of expected behaviors for these controls.

Apply consistent visibility and update logic patterns across
propulsion (impulse, warp, jump) and combat maneuver control
wrappers.

This prevents inconsistent UI behaviors when adding, removing,
and changing their related components at runtime.

Also align header guards on use of #pragma once, and remove
unnecessary warp_controls and jump_controls pointers from Helms now
that visibility logic is consistently handled in the wrapper
components.
Add two new helm keybindings:

- helms_warp_max: Request maximum warp level, parallel to max impulse
  and max jump keybinds. Accommodates warp drives with max_level > 4.
- helms_set_warp: Set warp request via joystick axis with simulated
  detents at each warp level.
Remove outdated documentation suggesting warp controls are limited
to factor 4.
If a ship has a docking port, disable sliders on warp, impulse,
and combat maneuver controls, and the Jump button on jump controls,
while docking or docked. Re-enable them when undocked. This reduces
the ambiguity of expected behaviors for these controls.
@oznogon oznogon marked this pull request as ready for review February 20, 2026 01:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant