Mission Planner UI Bug on Korean Language : Map zoom bar disappears on Flight Data tab

Ground Control Software Mission Planner
1

Environment

  • Mission Planner: 1.3.83, build 1.3.9384.38258 (stock build, no plugins/mods)

  • OS: Windows 10/11

  • UI Language: Korean (한국어, ko-KR)

  • Reproduced on multiple machines including a fresh Windows laptop where Mission Planner had never been customized or loaded any plugin.

Summary On the Flight Data tab, the vertical zoom slider (TRK_zoom) on the right side of the map is positioned ~69 px past the parent panel’s right edge when the UI culture is ko-KR, so it is rendered outside the visible area and effectively invisible. In every other locale (including the en default) the control is positioned correctly. Mouse-wheel zoom still works, but in the open sea, If the map is over-zoomed and a Guided command is issued, a drone took off from a ship can end up in danger.

Screenshots

Steps to reproduce

  1. Install stock Mission Planner 1.3.83 b9384 (no plugins, no modifications) on a clean machine.

  2. Open Mission Planner with the default (English) UI → zoom bar visible on the right side of the Flight Data map.

  3. Config → Planner → UI Language: 한국어 (Korean).

  4. Restart Mission Planner.

  5. Open the Flight Data tab → zoom bar is no longer visible.

Expected The zoom bar should be displayed regardless of the selected UI culture.

Actual TRK_zoom is offset roughly 69 px to the right of its parent’s right edge under ko-KR, so it is clipped out of the visible area. All other map overlays (HUD, compass, mode buttons, mavlink inspector) are unaffected.

Root cause

This is a defect in Mission Planner’s own localized resource file GCSViews/FlightData.ko-KR.resx. The Korean resx overrides splitContainer1.Size with a smaller width than the base resx, which is incompatible with the design-time anchor of TRK_zoom baked into the base form.

Base GCSViews/FlightData.resx:

xml

<data name="splitContainer1.Size" type="System.Drawing.Size, System.Drawing">
  <value>595, 411</value>
</data>

Korean GCSViews/FlightData.ko-KR.resx (lines ~4540-4542):

xml

<data name="splitContainer1.Size" type="System.Drawing.Size, System.Drawing">
  <value>526, 416</value>
</data>

TRK_zoom design-time properties (from base resx):

  • Location = (550, 40)

  • Size = (45, 157)

  • Anchor = Top, Bottom, Right

  • Right edge = 550 + 45 = 595

Because Anchor = Right preserves the design-time gap between the control’s right edge and the parent’s right edge for the lifetime of the form, the parent’s design-time width is what dictates where TRK_zoom ends up after the form is resized at runtime.

  • In the default culture, Panel2.Width = 595 at construction time, so the design-time gap is 595 − 595 = 0. The zoom bar tracks the parent’s right edge correctly.

  • In ko-KR, the ComponentResourceManager.ApplyResources call replays the splitContainer1.Size = (526, 416) override, so Panel2.Width = 526. The design-time gap becomes 526 − 595 = −69 (i.e. the control already extends 69 px past the parent’s right edge). The Right anchor preserves this -69 gap forever, so once the form is enlarged to e.g. Panel2.Width = 1329, the runtime position is TRK_zoom.X = 1329 + 69 − 45 = 1353, well outside the visible client area.

Empirical verification with a runtime probe matched the math exactly: Parent.ClientSize.Width = 1329, TRK_zoom.Location.X = 1353, i.e. 69 px outside the parent.

This behavior is therefore intrinsic to Mission Planner — it reproduces on a fresh, untouched install, with no plugins, no theme changes, and no custom builds. The bug is in the shipped FlightData.ko-KR.resx itself.

Solution

Aligning splitContainer1.Size in FlightData.ko-KR.resx with the base value (595, 411), or removing the override altogether, restores the zoom bar after a clean rebuild.

Question

Is the splitContainer1.Size = 526, 416 override in FlightData.ko-KR.resx intentional, or simply a stale value left behind by the WinForms designer?