Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@pull
Copy link

@pull pull bot commented Oct 8, 2025

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? đź’– Please sponsor : )

…anged`

The `textChanged` variable created ambiguity, since `TextFields` already
have a `textChanged()` signal. It was thus unclear when the
`onTextChanged` slot was triggered.

Renaming the `textChanged` property to `exprTextChanged` ensures that
`onTextChanged` is only triggered when the content of the text field
itself is changed by the user.
…hanged

This prevents validating default `evaluatedValue` when the user has not
performed any change.
If the `ExpressionTextField` is meant for an integer (`isInt = true`),
then the value of the expression should be an integer, meaning rounding
may need to be applied. However, for floating numbers, we do not want
to lose some precision, so the value should never be rounded or set
to a fixed number of decimal digits.
Floating numbers should not have a fixed number of decimals to avoid
losing precision, so the `decimals` property is not needed anymore.

References to it are removed in the HdrImageToolbar.
[qml] ExpressionTextFields: Fix unwanted value updates
@pull pull bot locked and limited conversation to collaborators Oct 8, 2025
@pull pull bot merged commit 7cac2bf into parampavar:develop Oct 8, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant