2021-07-23 09:44:38 +00:00
|
|
|
import QtQuick 2.14
|
|
|
|
|
import QtQuick.Controls 2.14
|
|
|
|
|
import QtQuick.Layouts 1.14
|
|
|
|
|
import StatusQ.Core 0.1
|
|
|
|
|
import StatusQ.Core.Theme 0.1
|
|
|
|
|
import StatusQ.Controls 0.1
|
feat(StatusInput): introduce new validator pipeline
There's a new `validators` property that can be used to add validators to `StatusInput` instances, which are executed in the same order:
```qml
StatusInput {
text: "Some value"
validators: [...]
}
```
For convenience StatusQ provides some common validation methods, such as `StatusMinLengthValidator`, StatusMaxLengthValidator` and could be extended to other (e.g. email validation etc):
```qml
StatusInput {
text: "Some value"
validators: [
StatusMinLengthValidator { minLength: 3 }
]
}
```
Validators are executed every time the text of the input changes. They are executed in the same order they have been applied, which enables users to create cascading conditions like "First make sure the value is at least 3 characters long, then make sure it matches a certain pattern".
When a validation fails, it sets the validity of the input (`valid: false`) accordingly and optionally exposes additional error information on `StatusInput.errors`:
```qml
StatusInput {
text: "Fo"
onTextChanged: {
if (errors) {
/**
* errors now has the following structure:
* errors: {
* minLength: { minValue: 3, actual: ... }
* }
* Also, `StatusInput` is now `valid = false`
**/
errorMesssage = "Expected " + errors.minLenght.minValue + " but got: "+ errors.minLength.actual; // i18n'able
}
}
validators: [
StatusMinLengthValidator { minLength: 3 }
]
}
```
There can be any number of error objects on the `errors` property, depending on who many validators have been run that failed validation.
Custom validators can be implemented by introducing a new `StatusValidator` type that has to implement a `validate()` function and defines the validators name. The `validate()` function has to return either `true` or `false` depending on whether the value is valid.
Alternatively, the function can return an error object which gets exposed on the underlying input's `errors` property, at which point it's considered invalid as well.
Here's a simple custom validator:
```qml
// HelloValidator.qml
import StatusQ.Controls.Validators 0.1
StatusValidator {
property string name: "hello"
validate: function (value) { // `value` is the `text` value of the underlying control
return value === "hello"
}
}
```
Applying this validators would look like this:
```qml
StatusInput {
text: "Some value"
validators: [
HelloValidator {}
]
onTextChanged: {
if (errors.hello) {
errorMessage = "Doesn't say hello!"
}
}
}
```
Alternatively, validators can return error objects to provide more information about what went wrong. Here's the implementation of the `StatusMinLengthValidator` as an example:
```qml
StatusValidator {
property int minLength: 0
name: "minLength"
validate: function (value) {
return value.length >= minLength ? true : {
min: minLength,
actual: value.length
}
}
}
```
Because validators as components, they can hold any custom properties they need to be configured.
There has been concern that, with this API, error messages need to be potentially defined in multiple places, given that there could be multiple instances of any validator. This is easily solved by having a centralized function figure out what the error message is, given a certain error object:
```qml
StatusInput {
validators: [
StatusMinLengthValidator { minLength: 3 }
]
onTextChanged: {
if (errors) {
errorMessage = getErrorMessage(errors) // this function is provided by global or elsewhere
}
}
}
```
Closes #298
2021-08-13 11:37:26 +00:00
|
|
|
import StatusQ.Controls.Validators 0.1
|
2021-07-23 09:44:38 +00:00
|
|
|
|
|
|
|
|
import Sandbox 0.1
|
|
|
|
|
|
|
|
|
|
Column {
|
|
|
|
|
spacing: 8
|
|
|
|
|
|
2021-07-23 10:36:45 +00:00
|
|
|
StatusInput {
|
|
|
|
|
input.placeholderText: "Placeholder"
|
2021-07-23 09:44:38 +00:00
|
|
|
}
|
|
|
|
|
|
2021-07-23 10:36:45 +00:00
|
|
|
StatusInput {
|
2021-07-23 11:17:14 +00:00
|
|
|
label: "Label"
|
2021-07-23 10:36:45 +00:00
|
|
|
input.placeholderText: "Disabled"
|
|
|
|
|
input.enabled: false
|
2021-07-23 09:44:38 +00:00
|
|
|
}
|
|
|
|
|
|
2021-07-23 10:36:45 +00:00
|
|
|
StatusInput {
|
|
|
|
|
input.placeholderText: "Clearable"
|
|
|
|
|
input.clearable: true
|
2021-07-23 10:02:00 +00:00
|
|
|
}
|
|
|
|
|
|
2021-07-23 10:36:45 +00:00
|
|
|
StatusInput {
|
|
|
|
|
input.placeholderText: "Invalid"
|
|
|
|
|
input.valid: false
|
2021-07-23 10:07:51 +00:00
|
|
|
}
|
|
|
|
|
|
2021-07-23 10:36:45 +00:00
|
|
|
StatusInput {
|
2021-07-26 12:57:30 +00:00
|
|
|
label: "Label"
|
|
|
|
|
|
|
|
|
|
input.icon.name: "search"
|
|
|
|
|
input.placeholderText: "Input with icon"
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
StatusInput {
|
2021-07-23 10:36:45 +00:00
|
|
|
label: "Label"
|
|
|
|
|
input.placeholderText: "Placeholder"
|
2021-07-23 11:17:14 +00:00
|
|
|
input.clearable: true
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
StatusInput {
|
|
|
|
|
charLimit: 30
|
|
|
|
|
input.placeholderText: "Placeholder"
|
|
|
|
|
input.clearable: true
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
StatusInput {
|
|
|
|
|
label: "Label"
|
|
|
|
|
charLimit: 30
|
|
|
|
|
input.placeholderText: "Placeholder"
|
|
|
|
|
input.clearable: true
|
|
|
|
|
}
|
|
|
|
|
|
2022-03-09 23:13:20 +00:00
|
|
|
Item {
|
|
|
|
|
implicitWidth: 480
|
|
|
|
|
implicitHeight: 102
|
|
|
|
|
z: 100000
|
|
|
|
|
StatusSeedPhraseInput {
|
|
|
|
|
id: statusSeedInput
|
|
|
|
|
anchors.left: parent.left
|
|
|
|
|
anchors.right: parent.right
|
|
|
|
|
textEdit.input.anchors.leftMargin: 16
|
|
|
|
|
textEdit.input.anchors.rightMargin: 16
|
|
|
|
|
textEdit.input.anchors.topMargin: 11
|
|
|
|
|
textEdit.label: "Input with drop down selection list"
|
|
|
|
|
leftComponentText: "1"
|
|
|
|
|
inputList: ListModel {
|
|
|
|
|
ListElement {
|
|
|
|
|
seedWord: "panda"
|
|
|
|
|
}
|
|
|
|
|
ListElement {
|
|
|
|
|
seedWord: "posible"
|
|
|
|
|
}
|
|
|
|
|
ListElement {
|
|
|
|
|
seedWord: "wing"
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2021-07-23 11:17:14 +00:00
|
|
|
StatusInput {
|
|
|
|
|
label: "Label"
|
|
|
|
|
charLimit: 30
|
|
|
|
|
errorMessage: "Error message"
|
|
|
|
|
|
|
|
|
|
input.clearable: true
|
|
|
|
|
input.valid: false
|
|
|
|
|
input.placeholderText: "Placeholder"
|
2021-07-23 09:44:38 +00:00
|
|
|
}
|
|
|
|
|
|
2021-09-01 16:53:48 +00:00
|
|
|
StatusInput {
|
|
|
|
|
label: "StatusInput"
|
|
|
|
|
secondaryLabel: "with right icon"
|
|
|
|
|
input.icon.width: 15
|
|
|
|
|
input.icon.height: 11
|
|
|
|
|
input.icon.name: text !== "" ? "checkmark" : ""
|
|
|
|
|
input.leftIcon: false
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
StatusInput {
|
|
|
|
|
label: "Label"
|
|
|
|
|
secondaryLabel: "secondary label"
|
|
|
|
|
input.placeholderText: "Placeholder"
|
|
|
|
|
input.implicitHeight: 56
|
|
|
|
|
}
|
|
|
|
|
|
feat(StatusInput): introduce new validator pipeline
There's a new `validators` property that can be used to add validators to `StatusInput` instances, which are executed in the same order:
```qml
StatusInput {
text: "Some value"
validators: [...]
}
```
For convenience StatusQ provides some common validation methods, such as `StatusMinLengthValidator`, StatusMaxLengthValidator` and could be extended to other (e.g. email validation etc):
```qml
StatusInput {
text: "Some value"
validators: [
StatusMinLengthValidator { minLength: 3 }
]
}
```
Validators are executed every time the text of the input changes. They are executed in the same order they have been applied, which enables users to create cascading conditions like "First make sure the value is at least 3 characters long, then make sure it matches a certain pattern".
When a validation fails, it sets the validity of the input (`valid: false`) accordingly and optionally exposes additional error information on `StatusInput.errors`:
```qml
StatusInput {
text: "Fo"
onTextChanged: {
if (errors) {
/**
* errors now has the following structure:
* errors: {
* minLength: { minValue: 3, actual: ... }
* }
* Also, `StatusInput` is now `valid = false`
**/
errorMesssage = "Expected " + errors.minLenght.minValue + " but got: "+ errors.minLength.actual; // i18n'able
}
}
validators: [
StatusMinLengthValidator { minLength: 3 }
]
}
```
There can be any number of error objects on the `errors` property, depending on who many validators have been run that failed validation.
Custom validators can be implemented by introducing a new `StatusValidator` type that has to implement a `validate()` function and defines the validators name. The `validate()` function has to return either `true` or `false` depending on whether the value is valid.
Alternatively, the function can return an error object which gets exposed on the underlying input's `errors` property, at which point it's considered invalid as well.
Here's a simple custom validator:
```qml
// HelloValidator.qml
import StatusQ.Controls.Validators 0.1
StatusValidator {
property string name: "hello"
validate: function (value) { // `value` is the `text` value of the underlying control
return value === "hello"
}
}
```
Applying this validators would look like this:
```qml
StatusInput {
text: "Some value"
validators: [
HelloValidator {}
]
onTextChanged: {
if (errors.hello) {
errorMessage = "Doesn't say hello!"
}
}
}
```
Alternatively, validators can return error objects to provide more information about what went wrong. Here's the implementation of the `StatusMinLengthValidator` as an example:
```qml
StatusValidator {
property int minLength: 0
name: "minLength"
validate: function (value) {
return value.length >= minLength ? true : {
min: minLength,
actual: value.length
}
}
}
```
Because validators as components, they can hold any custom properties they need to be configured.
There has been concern that, with this API, error messages need to be potentially defined in multiple places, given that there could be multiple instances of any validator. This is easily solved by having a centralized function figure out what the error message is, given a certain error object:
```qml
StatusInput {
validators: [
StatusMinLengthValidator { minLength: 3 }
]
onTextChanged: {
if (errors) {
errorMessage = getErrorMessage(errors) // this function is provided by global or elsewhere
}
}
}
```
Closes #298
2021-08-13 11:37:26 +00:00
|
|
|
StatusInput {
|
2021-09-10 10:44:38 +00:00
|
|
|
id: input
|
feat(StatusInput): introduce new validator pipeline
There's a new `validators` property that can be used to add validators to `StatusInput` instances, which are executed in the same order:
```qml
StatusInput {
text: "Some value"
validators: [...]
}
```
For convenience StatusQ provides some common validation methods, such as `StatusMinLengthValidator`, StatusMaxLengthValidator` and could be extended to other (e.g. email validation etc):
```qml
StatusInput {
text: "Some value"
validators: [
StatusMinLengthValidator { minLength: 3 }
]
}
```
Validators are executed every time the text of the input changes. They are executed in the same order they have been applied, which enables users to create cascading conditions like "First make sure the value is at least 3 characters long, then make sure it matches a certain pattern".
When a validation fails, it sets the validity of the input (`valid: false`) accordingly and optionally exposes additional error information on `StatusInput.errors`:
```qml
StatusInput {
text: "Fo"
onTextChanged: {
if (errors) {
/**
* errors now has the following structure:
* errors: {
* minLength: { minValue: 3, actual: ... }
* }
* Also, `StatusInput` is now `valid = false`
**/
errorMesssage = "Expected " + errors.minLenght.minValue + " but got: "+ errors.minLength.actual; // i18n'able
}
}
validators: [
StatusMinLengthValidator { minLength: 3 }
]
}
```
There can be any number of error objects on the `errors` property, depending on who many validators have been run that failed validation.
Custom validators can be implemented by introducing a new `StatusValidator` type that has to implement a `validate()` function and defines the validators name. The `validate()` function has to return either `true` or `false` depending on whether the value is valid.
Alternatively, the function can return an error object which gets exposed on the underlying input's `errors` property, at which point it's considered invalid as well.
Here's a simple custom validator:
```qml
// HelloValidator.qml
import StatusQ.Controls.Validators 0.1
StatusValidator {
property string name: "hello"
validate: function (value) { // `value` is the `text` value of the underlying control
return value === "hello"
}
}
```
Applying this validators would look like this:
```qml
StatusInput {
text: "Some value"
validators: [
HelloValidator {}
]
onTextChanged: {
if (errors.hello) {
errorMessage = "Doesn't say hello!"
}
}
}
```
Alternatively, validators can return error objects to provide more information about what went wrong. Here's the implementation of the `StatusMinLengthValidator` as an example:
```qml
StatusValidator {
property int minLength: 0
name: "minLength"
validate: function (value) {
return value.length >= minLength ? true : {
min: minLength,
actual: value.length
}
}
}
```
Because validators as components, they can hold any custom properties they need to be configured.
There has been concern that, with this API, error messages need to be potentially defined in multiple places, given that there could be multiple instances of any validator. This is easily solved by having a centralized function figure out what the error message is, given a certain error object:
```qml
StatusInput {
validators: [
StatusMinLengthValidator { minLength: 3 }
]
onTextChanged: {
if (errors) {
errorMessage = getErrorMessage(errors) // this function is provided by global or elsewhere
}
}
}
```
Closes #298
2021-08-13 11:37:26 +00:00
|
|
|
label: "Label"
|
|
|
|
|
charLimit: 30
|
|
|
|
|
input.placeholderText: "Input with validator"
|
|
|
|
|
|
|
|
|
|
validators: [
|
2021-09-10 10:44:38 +00:00
|
|
|
StatusMinLengthValidator {
|
|
|
|
|
minLength: 10
|
|
|
|
|
errorMessage: {
|
|
|
|
|
if (input.errors && input.errors.minLength) {
|
|
|
|
|
return `Value can't be shorter than ${input.errors.minLength.min} but got ${input.errors.minLength.actual}`
|
|
|
|
|
}
|
|
|
|
|
return ""
|
|
|
|
|
}
|
feat(StatusInput): introduce new validator pipeline
There's a new `validators` property that can be used to add validators to `StatusInput` instances, which are executed in the same order:
```qml
StatusInput {
text: "Some value"
validators: [...]
}
```
For convenience StatusQ provides some common validation methods, such as `StatusMinLengthValidator`, StatusMaxLengthValidator` and could be extended to other (e.g. email validation etc):
```qml
StatusInput {
text: "Some value"
validators: [
StatusMinLengthValidator { minLength: 3 }
]
}
```
Validators are executed every time the text of the input changes. They are executed in the same order they have been applied, which enables users to create cascading conditions like "First make sure the value is at least 3 characters long, then make sure it matches a certain pattern".
When a validation fails, it sets the validity of the input (`valid: false`) accordingly and optionally exposes additional error information on `StatusInput.errors`:
```qml
StatusInput {
text: "Fo"
onTextChanged: {
if (errors) {
/**
* errors now has the following structure:
* errors: {
* minLength: { minValue: 3, actual: ... }
* }
* Also, `StatusInput` is now `valid = false`
**/
errorMesssage = "Expected " + errors.minLenght.minValue + " but got: "+ errors.minLength.actual; // i18n'able
}
}
validators: [
StatusMinLengthValidator { minLength: 3 }
]
}
```
There can be any number of error objects on the `errors` property, depending on who many validators have been run that failed validation.
Custom validators can be implemented by introducing a new `StatusValidator` type that has to implement a `validate()` function and defines the validators name. The `validate()` function has to return either `true` or `false` depending on whether the value is valid.
Alternatively, the function can return an error object which gets exposed on the underlying input's `errors` property, at which point it's considered invalid as well.
Here's a simple custom validator:
```qml
// HelloValidator.qml
import StatusQ.Controls.Validators 0.1
StatusValidator {
property string name: "hello"
validate: function (value) { // `value` is the `text` value of the underlying control
return value === "hello"
}
}
```
Applying this validators would look like this:
```qml
StatusInput {
text: "Some value"
validators: [
HelloValidator {}
]
onTextChanged: {
if (errors.hello) {
errorMessage = "Doesn't say hello!"
}
}
}
```
Alternatively, validators can return error objects to provide more information about what went wrong. Here's the implementation of the `StatusMinLengthValidator` as an example:
```qml
StatusValidator {
property int minLength: 0
name: "minLength"
validate: function (value) {
return value.length >= minLength ? true : {
min: minLength,
actual: value.length
}
}
}
```
Because validators as components, they can hold any custom properties they need to be configured.
There has been concern that, with this API, error messages need to be potentially defined in multiple places, given that there could be multiple instances of any validator. This is easily solved by having a centralized function figure out what the error message is, given a certain error object:
```qml
StatusInput {
validators: [
StatusMinLengthValidator { minLength: 3 }
]
onTextChanged: {
if (errors) {
errorMessage = getErrorMessage(errors) // this function is provided by global or elsewhere
}
}
}
```
Closes #298
2021-08-13 11:37:26 +00:00
|
|
|
}
|
2021-09-10 10:44:38 +00:00
|
|
|
]
|
feat(StatusInput): introduce new validator pipeline
There's a new `validators` property that can be used to add validators to `StatusInput` instances, which are executed in the same order:
```qml
StatusInput {
text: "Some value"
validators: [...]
}
```
For convenience StatusQ provides some common validation methods, such as `StatusMinLengthValidator`, StatusMaxLengthValidator` and could be extended to other (e.g. email validation etc):
```qml
StatusInput {
text: "Some value"
validators: [
StatusMinLengthValidator { minLength: 3 }
]
}
```
Validators are executed every time the text of the input changes. They are executed in the same order they have been applied, which enables users to create cascading conditions like "First make sure the value is at least 3 characters long, then make sure it matches a certain pattern".
When a validation fails, it sets the validity of the input (`valid: false`) accordingly and optionally exposes additional error information on `StatusInput.errors`:
```qml
StatusInput {
text: "Fo"
onTextChanged: {
if (errors) {
/**
* errors now has the following structure:
* errors: {
* minLength: { minValue: 3, actual: ... }
* }
* Also, `StatusInput` is now `valid = false`
**/
errorMesssage = "Expected " + errors.minLenght.minValue + " but got: "+ errors.minLength.actual; // i18n'able
}
}
validators: [
StatusMinLengthValidator { minLength: 3 }
]
}
```
There can be any number of error objects on the `errors` property, depending on who many validators have been run that failed validation.
Custom validators can be implemented by introducing a new `StatusValidator` type that has to implement a `validate()` function and defines the validators name. The `validate()` function has to return either `true` or `false` depending on whether the value is valid.
Alternatively, the function can return an error object which gets exposed on the underlying input's `errors` property, at which point it's considered invalid as well.
Here's a simple custom validator:
```qml
// HelloValidator.qml
import StatusQ.Controls.Validators 0.1
StatusValidator {
property string name: "hello"
validate: function (value) { // `value` is the `text` value of the underlying control
return value === "hello"
}
}
```
Applying this validators would look like this:
```qml
StatusInput {
text: "Some value"
validators: [
HelloValidator {}
]
onTextChanged: {
if (errors.hello) {
errorMessage = "Doesn't say hello!"
}
}
}
```
Alternatively, validators can return error objects to provide more information about what went wrong. Here's the implementation of the `StatusMinLengthValidator` as an example:
```qml
StatusValidator {
property int minLength: 0
name: "minLength"
validate: function (value) {
return value.length >= minLength ? true : {
min: minLength,
actual: value.length
}
}
}
```
Because validators as components, they can hold any custom properties they need to be configured.
There has been concern that, with this API, error messages need to be potentially defined in multiple places, given that there could be multiple instances of any validator. This is easily solved by having a centralized function figure out what the error message is, given a certain error object:
```qml
StatusInput {
validators: [
StatusMinLengthValidator { minLength: 3 }
]
onTextChanged: {
if (errors) {
errorMessage = getErrorMessage(errors) // this function is provided by global or elsewhere
}
}
}
```
Closes #298
2021-08-13 11:37:26 +00:00
|
|
|
}
|
|
|
|
|
|
2022-03-10 15:33:10 +00:00
|
|
|
StatusInput {
|
|
|
|
|
label: "Input with <i>StatusRegularExpressionValidator</i>"
|
|
|
|
|
charLimit: 30
|
|
|
|
|
input.placeholderText: `Must match regex(${validators[0].regularExpression.toString()}) and <= 30 chars`
|
|
|
|
|
validationMode: StatusInput.ValidationMode.IgnoreInvalidInput
|
|
|
|
|
|
|
|
|
|
validators: [
|
|
|
|
|
StatusRegularExpressionValidator {
|
|
|
|
|
regularExpression: /^[0-9A-Za-z_\$-\s]*$/
|
|
|
|
|
errorMessage: "Bad input!"
|
|
|
|
|
}
|
|
|
|
|
]
|
|
|
|
|
}
|
|
|
|
|
|
2021-09-07 10:52:13 +00:00
|
|
|
StatusInput {
|
|
|
|
|
label: "Label"
|
|
|
|
|
input.placeholderText: "Input width component (right side)"
|
2022-03-18 12:08:02 +00:00
|
|
|
input.rightComponent: StatusIcon {
|
2021-09-07 10:52:13 +00:00
|
|
|
icon: "cancel"
|
|
|
|
|
height: 16
|
|
|
|
|
color: Theme.palette.dangerColor1
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
2021-07-23 10:36:45 +00:00
|
|
|
StatusInput {
|
|
|
|
|
input.multiline: true
|
|
|
|
|
input.placeholderText: "Multiline"
|
2021-07-23 09:44:38 +00:00
|
|
|
}
|
|
|
|
|
|
2021-07-23 10:36:45 +00:00
|
|
|
StatusInput {
|
|
|
|
|
input.multiline: true
|
|
|
|
|
input.placeholderText: "Multiline with static height"
|
|
|
|
|
input.implicitHeight: 100
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
StatusInput {
|
|
|
|
|
input.multiline: true
|
|
|
|
|
input.placeholderText: "Multiline with max/min"
|
|
|
|
|
input.minimumHeight: 80
|
|
|
|
|
input.maximumHeight: 200
|
2021-07-23 09:44:38 +00:00
|
|
|
}
|
2022-03-11 19:34:21 +00:00
|
|
|
|
|
|
|
|
StatusInput {
|
2022-03-18 12:08:02 +00:00
|
|
|
property bool toggled: true
|
2022-03-11 19:34:21 +00:00
|
|
|
label: "Input with emoji icon"
|
|
|
|
|
input.placeholderText: "Enter Name"
|
2022-03-18 12:08:02 +00:00
|
|
|
input.icon.emoji: toggled ? "😁" : "🧸"
|
2022-03-11 19:34:21 +00:00
|
|
|
input.icon.color: "blue"
|
|
|
|
|
input.isIconSelectable: true
|
|
|
|
|
onIconClicked: {
|
2022-03-18 12:08:02 +00:00
|
|
|
toggled = !toggled
|
2022-03-11 19:34:21 +00:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
StatusInput {
|
2022-03-18 12:08:02 +00:00
|
|
|
property bool toggled: true
|
2022-03-11 19:34:21 +00:00
|
|
|
label: "Input with selectable icon which is not an emoji"
|
|
|
|
|
input.placeholderText: "Enter Name"
|
|
|
|
|
input.icon.emoji: ""
|
2022-03-18 12:08:02 +00:00
|
|
|
input.icon.name: toggled ? "filled-account" : "image"
|
2022-03-11 19:34:21 +00:00
|
|
|
input.icon.color: "blue"
|
|
|
|
|
input.isIconSelectable: true
|
|
|
|
|
onIconClicked: {
|
2022-03-18 12:08:02 +00:00
|
|
|
toggled = !toggled
|
2022-03-11 19:34:21 +00:00
|
|
|
}
|
|
|
|
|
}
|
2022-03-22 08:56:58 +00:00
|
|
|
|
|
|
|
|
StatusInput {
|
|
|
|
|
label: "Input with inline token selector"
|
|
|
|
|
input.leftComponent: StatusTokenInlineSelector {
|
|
|
|
|
tokens: [{amount: 0.1, token: "ETH"},
|
|
|
|
|
{amount: 10, token: "SNT"},
|
|
|
|
|
{amount: 15, token: "MANA"}]
|
|
|
|
|
|
|
|
|
|
StatusToolTip {
|
|
|
|
|
id: toolTip
|
|
|
|
|
text: "posted"
|
|
|
|
|
}
|
|
|
|
|
onTriggered: toolTip.visible = true
|
|
|
|
|
}
|
|
|
|
|
input.edit.readOnly: true
|
|
|
|
|
}
|
2021-07-23 09:44:38 +00:00
|
|
|
}
|
