Before logging an issue, make sure that you have updated ng-formworks to the latest patch level for the corresponding version of Angular that you are using, then test again to see if the issue persists

Describe the bug
which version of ng-formworks:

• 15.x.x
• 16.x.x
• 17.x.x
• 18.x.x
• 19.x.x

which version of Angular:

• 15
• 16
• 17
• 18
• 19

which framework:

• MaterialDesignFrameworkModule — Material Design
• Bootstrap3FrameworkModule — Bootstrap 3
• Bootstrap4FrameworkModule — Bootstrap 4
• Bootstrap5FrameworkModule — Bootstrap 5
• DaisyUIFrameworkModule — DaisyUI
• NoFrameworkModule — plain HTML
• Other (please specify below)

A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

In this playground example the checkbox does not deselect properly when it is used as condition for showing/hiding another field or object.

The form is initially displayed with the Has a Reset Timer checkbox unselected and the Reset Timer object/section is not displayed:

The Has a Reset Timer checkbox is clicked, it is displayed as selected and the Reset Timer object/section is displayed:

The Has a Reset Timer checkbox is clicked, it is still displayed as selected when it should be displayed as unselected and the Reset Timer object/section is not displayed:

It requires a second click to deselect the Has a Reset Timer checkbox.

The Has a Companion Sensor checkbox is defined exactly as the Has a Reset Timer checkbox,, but is not used as a condition for showing/hiding another field or object. It correctly displays as selected and unselected when clicked.