Updates in general was only done if a POI changed. This caused changes related to something other than a change in POI to be ignore. The code now "resets" the POI when such changes occur (change of ruleset for example).
Ruleset selection is was not persistent. When reloading the list of rulesets for a given region, any previously selected ruleset would be reset to defaults.
Also fixed several new clang warnings.

It seems the icons now use dash instead of underscore. I'm simply replacing dash by underscore wholesale (to match the existing resource names) until I know better.

Change feature default values to something that will be identified as "not set". When a flight is created, features with missing values (not set) are not included. Note that all these are persistent, which may create a problem if something changes (different vehicle with large weight difference for instance). As the subsequent use of these are persistent, a question may not be asked because it's already set (the brief only asks for missing or problem values).

Make the choice of using a personal key persistent. This will allow to toggle between personal and hardcoded key. Otherwise you would need to clear your personal key each time you want to use the hardcoded one.

The build system will look for src/Airmap/Airmap_api_key.h
If it find is, it will used the provided API key and client ID for Airmap.
That file should provide two strings:
static const char* kAirmapAPIKey = "key data";
static const char* kAirmapClientID = "id data";

Local builds, without these will have no Airmap support by default (users can always enter their own within the Airmap settings panel).

It builds clean but the resources still get messed up (loads true qml files instead of dummy ones, and it crashes...)

Add message asking user confirmation to end a flight

Remove delete flights and add "End" active flight instead
Work on flight geometry (flight list)

Implementing authorization management

Flight management with date range, delete flights.

Cleaning up old vehicle manager and getting it ready to actually provide services for a vehicle (flight management)
Added submit flight plan
Added update flight plan
Disable flight features as these don't seem to be quite working (values must be initialized and validated before submission as backend doesn't validate and the objects don't initialize their members)

Have different modes for the Airspace Widget (Plan/Fly)

Permit refactoring
QGCButton tweaks

Make all argument to AirMap queries based on what the screen shows (bounding rectangle and/or radius), respecting the limits imposed by AirMap.

Collect rulesets from briefing