# fix\(qml\): replace Qt.NoButton with 0 to fix qmllint error · lucenx/codexbar-plasma

[View on GitCafe](https://git.cafe/lucenx/codexbar-plasma/commit/53afc7c92ca34869e6e8ce37b5d6da792bde882e)

Repository: [lucenx/codexbar-plasma](https://git.cafe/lucenx/codexbar-plasma)

Visibility: public

Requested revision: 53afc7c92ca34869e6e8ce37b5d6da792bde882e

Requested commit: 53afc7c92ca34869e6e8ce37b5d6da792bde882e

Commit: 53afc7c92ca34869e6e8ce37b5d6da792bde882e

Tree: bd78d69d06164c62030618d90912194f916b04a9

Author: google-labs-jules\[bot\]

Committer: google-labs-jules\[bot\]

## Message

```
fix(qml): replace Qt.NoButton with 0 to fix qmllint error

In Qt 6 QML, strict `qmllint` mode can incorrectly report that
the `NoButton` property is not found on the `Qt` namespace when
evaluating bindings. This causes builds or test runs validating
with `--missing-property` checks to fail unnecessarily.

This commit replaces `Qt.NoButton` with its equivalent integer
value `0` in `CompactRepresentation.qml` and `SpendView.qml`.
It maintains the exact same runtime behavior (making the
`MouseArea` components accept zero buttons and only respond to
hover events) but sidesteps the qmllint evaluation issue.

The UI regression tests have also been updated to ensure
the checks correctly match either `Qt.NoButton` or `0` moving
forward.

Co-authored-by: Lucenx9 <185146821+Lucenx9@users.noreply.github.com>

```

## Parents

- [903cc632d2928928a36746f6b8242b272439caa6](https://git.cafe/lucenx/codexbar-plasma/commit/903cc632d2928928a36746f6b8242b272439caa6?format=markdown)

[Source at this commit](https://git.cafe/lucenx/codexbar-plasma/tree/53afc7c92ca34869e6e8ce37b5d6da792bde882e?format=markdown)