Feature: Add QML-configurable gimbal max speed and deadzones

[Niki-dev12]

Title:

Add QML-configurable gimbal max speed and yaw/pitch deadzone settings

Description

This PR adds new joystick configuration features to allow runtime adjustment of: Gimbal pitch and yaw max speed, using a single gimbalMaxSpeed parameter exposed to QML Deadzone control for pitch and yaw gimbal axes via gimbalPitchDeadzone and gimbalYawDeadzone Enable/disable axis-based gimbal control (gimbalAxisEnabled)

This allows users to fine-tune gimbal behavior without recompiling, which is especially useful when mapping joystick axes for dynamic camera control.

Changes include:

Q_PROPERTY bindings for the three settings
Persistent saving and loading through _saveSettings() and _loadSettings()
Updated _handleAxis() to apply speed scaling and deadzone filtering
Optional offset for gimbal pitch and yaw to avoid zero drift

Test Steps

Launch QGC with a joystick connected
Use a QML debug view or a settings panel to:
    Set gimbalMaxSpeed (e.g., 30–160)
    Adjust gimbalPitchDeadzone or gimbalYawDeadzone
    Toggle gimbalAxisEnabled
Observe how gimbal responsiveness changes accordingly
Confirm values persist between sessions

Tested in:

Real drone running ardupilot with gimbal
Ubuntu 22 and Zorro 

Checklist:

• [ X] Review Contribution Guidelines.
• [ X] Review Code of Conduct.
• [ X] I have tested my changes.

Related Issue

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[HTRamsey]

Could you look at the GimbalController and see if you can use that instead of changing Vehicle?

[Niki-dev12]

This is starting to look good.

Have you thought about the case where we don't have control over the gimbal yet and need to acquire it?

I suggest handling this in a follow up PR, since it feels a bit out of scope for the changes in this one.

[HTRamsey]

Could you remove the extra .txt & .cmake files?

[Niki-dev12]

Could you remove the extra .txt & .cmake files?

Yes I will do that. Thanks for pointing it out.

[DonLakeFlyer]

So I've been going through the state of Joystick Config/Calibration. It's quite a mess and needs a consistent rework. I'm going to do that in the next couple days which is gonna hammer this pull. I'll take care of it myself though by integrating.modifying your work into the new code. So leave this open for now. And I'll pull code from it and move it to the new stuff as I make progress.

[Niki-dev12]

So I've been going through the state of Joystick Config/Calibration. It's quite a mess and needs a consistent rework. I'm going to do that in the next couple days which is gonna hammer this pull. I'll take care of it myself though by integrating.modifying your work into the new code. So leave this open for now. And I'll pull code from it and move it to the new stuff as I make progress.

Thanks a lot for the update. I will leave the PR open as suggested and will follow your progress.

[eMrazSVK]

Hi @DonLakeFlyer is there any update from your side on this?

[DonLakeFlyer]

Sorry, lost track of this. Working on it now...