This is a bit of a boolean trap.

We could declare an enum in QML
setCursorSettings(Busy | Blinking) would be a bit nicer maybe?

Up to you.

onToggled is called both when it is checked, and presumably when it is unchecked (or another button is checked)

I assume we want something more like:

onToggled: {if (!checked) return; formLayout.setCursorSettings(false,...}

taskar -> taskbar

Yes, I would prefer all of this to be abstracted away from the QML, the checked bindings area also quite messy

onToggled fires when user explicitly toggles it by clicking it. Given you can't "untoggle" a radio button should be fine-ish?

Use onValueModified which only fires when the user explicitly changes it, not because of some binding updates

I agree it's a bit tricky, we have a kind of enum choice written as a binary representation in the config file.

Will try to work it with a QML enum to make it less confusing.

According to Qt documentation :

This signal is emitted when a checkable button is interactively toggled by the user via touch, mouse, or keyboard.

Since it's a radio button, you can't uncheck it, so the signal is emitted only when checked. I've tested both as I first tought like david said.

Sounds better. wiil fix.

good catch, thanks. will fix.

Or... but that's more work and I'd say it should come in another patch on top of that one. We migrate the config file to use an enum all the way. This boolean trap exists in the config after all.

Added enum to remove the triple boolean parameter.

To solve the boolean trap, it means to change the config to an enum instead of 3 booleans. This patch is intended to port Launch Feedback to KConfig XT, we could fix the configuration issue in another patch.