Checklist

• I have searched existing enhancements and this is not a duplicate.
• This request covers a single enhancement (open a separate issue for each one).
• I have filled out the template below.

Adaptive Cover Pro version

2.27.0

Is your enhancement related to a problem?

Context

Two configuration pages currently expose partially overlapping concepts for defining
the horizontal sun-tracking zone:

In "Cover geometry"

• Window depth (reveal) — optional, defaults to 0
• When set > 0, it geometrically computes when direct sunlight enters/leaves the window
  based on the recess in the wall

In "Sun tracking"

• FOV left (default 85°)
• FOV right (default 85°)
• Defines the horizontal sun-tracking zone directly as two angles

)

The problem

From what I understand:

1. The two settings define the same thing (when does the sun "see" the window horizontally),
   but through two different mental models — geometric (depth) vs angular (FOV).
2. Window depth overrides / replaces FOV when set, which is confusing because nothing
   in the UI signals this dependency.
3. Users land on three sliders for what is essentially one concept, with no clear guidance
   on which one to use.

I really appreciate the simplification that "Window depth" brings (one intuitive measurement
instead of two abstract angles), but the current UI exposes both in parallel, which
defeats that simplification.

Describe the solution you'd like

Possible directions (open to discussion)

I don't have a definitive solution, but here are a few directions worth exploring:

Direction 1 — Mode selector

Add a single choice at the top of "Sun tracking":

• "Define horizontal tracking by:" → (a) Window depth / (b) FOV angles / (c) Auto from geometry

Then show only the relevant field(s). The other one is hidden, not just ignored.

Direction 2 — Move "Window depth" out of Geometry

Since window depth is functionally a sun-tracking parameter (it defines when light enters),
move it next to FOV left/right under "Sun tracking". Keep "Geometry" for pure cover/window
dimensions. This at least groups the overlapping concepts in one page where the precedence
can be made visible.

Direction 3 — Make the override explicit

Keep both pages as-is, but add a clear visual indicator:

• On the FOV sliders: "⚠ Overridden by Window depth (0.10 m) — set depth to 0 to use these values"
• On the Window depth slider: "Replaces FOV left/right when > 0"

Less elegant but non-breaking.

Direction 4 — Compute FOV from depth, show as read-only

When window depth > 0, automatically compute the equivalent FOV values and display them
read-only below, as feedback. Users see "you set depth = 10cm → effective FOV ≈ 78°/78°",
which teaches the relationship instead of hiding it.

Alternatives you've considered

No response

Additional context

No response