ArduPilot / ArduPilot/MissionPlanner

QuickView critical values are not visible while in other than FlightData view/Quick tab

Open
#1,609 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
2.4k
Forks
2.9k
Avg merge
19h 16m
Merged PRs (30d)
4

Description

#### Issue details
The issue is about observability of critical UAV state values while operating with UAV missions, payload, settings, etc.

When operator of UAV changed view to any other than FlightData view or operator switched to any tab other than Quick he can't observe QuickView values. Observing some values (Battery Voltage, RPM, Altitude, Climb Rate, etc) is critical for UAV operation. So operator can react immediately if one of critical parameter goes out of normal range. We need to have few of them (critical ones) always be visible in any GCS view. We may use ToolStrip for placing QuickViews.

Opening FlightPlan view in map pane is not a solution because it doesn't solve situation if tab switched to other than Quick.
#### Version
All
#### Platform
[ x ] All
[ ] AntennaTracker
[ ] Copter
[ ] Plane
[ ] Rover
[ ] Sub

#### Airframe type
All
#### Hardware type
Any

#### Logs
No Log needed

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing how QuickView values are rendered in the FlightData view and Quick tab, then inspect the other GCS views and tabs. Evaluate the suggested ToolStrip placement for keeping a small set of critical values visible everywhere. Done means selected values such as Battery Voltage, RPM, Altitude, and Climb Rate remain observable outside FlightData and Quick.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.