ArduPilot / ArduPilot/CustomBuild

Enable "sticky" features when changing FW type

Open
#237 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
32
Forks
74
PR merge metrics
No merged PRs in 30d

Description

I remember earlier we had the ability to keep the currently enabled features enabled and the disabled one disabled when switching to another firmware. Now the features get overwritten by the defaults when I switch to another FW.
For example, let us say I want to build a Pixhawk1-bdshot FW. I may not need all the features so I decide to start off from the -1M version and build on top of it by adding /removing features as removing features from the 2MB version will be more time consuming. But there is no button that keeps my current selections active as I switch but this used to exist a few months earlier.
I request to bring this back.
Thanks

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing the firmware-type switching flow and where the current feature selections are stored or replaced. Reproduce the switch from the 1M firmware to another firmware, then verify that enabled features remain enabled and disabled features remain disabled after switching.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.