feat(StatusBaseInput): introduce `dirty` and `pristine` properties

These properties can be used to determine whether a user has either
interacted with the form control, or changed its value.

It's also used in initial validation to ensure validation is done but
visually, form controls stay untouched.

Closes #327
This commit is contained in:
Pascal Precht 2021-08-16 14:21:55 +02:00 committed by Michał Cieślak
parent 3c6147c69c
commit 4fe2d82208
1 changed files with 10 additions and 1 deletions

View File

@ -43,6 +43,8 @@ Item {
property int maximumLength: 0
property bool valid: true
property bool pristine: true
property bool dirty: false
property StatusIconSettings icon: StatusIconSettings {
width: 24
@ -67,7 +69,7 @@ Item {
border.width: 1
border.color: {
if (!statusBaseInput.valid) {
if (!statusBaseInput.valid && statusBaseInput.dirty) {
return Theme.palette.dangerColor1;
}
if (edit.activeFocus) {
@ -144,6 +146,12 @@ Item {
onCursorRectangleChanged: flick.ensureVisible(cursorRectangle)
wrapMode: statusBaseInput.multiline ? Text.WrapAtWordBoundaryOrAnywhere : TextEdit.NoWrap
onActiveFocusChanged: {
if (statusBaseInput.pristine) {
statusBaseInput.pristine = false
}
}
Keys.onReturnPressed: {
if (multiline) {
event.accepted = false
@ -161,6 +169,7 @@ Item {
}
onTextChanged: {
statusBaseInput.dirty = true
if (statusBaseInput.maximumLength > 0) {
if (text.length > statusBaseInput.maximumLength) {
var cursor = cursorPosition;