A bug about Keyboard Focus in Qt Quick in QT 5.10 document?

[mrmuto2]

I am reading the Qt doc to learn the Keyboard Focus in Qt Quick! I run the code which from the document. However, the result is different form the document! The codes are as follows.

main.qml


//Window code that imports MyWidget
Rectangle {
id: window
color: "white"; width: 240; height: 150

Column {
anchors.centerIn: parent; spacing: 15

MyWidget {
focus: true //set this MyWidget to receive the focus
color: "lightblue"
}
MyWidget {
color: "palegreen"
}
}

MyWidget.qml


Rectangle {
id: widget
color: "lightsteelblue"; width: 175; height: 25; radius: 10; antialiasing:
true
Text { id: label; anchors.centerIn: parent}
focus: true
Keys.onPressed: {
if (event.key == Qt.Key_A)
label.text = 'Key A was pressed'
else if (event.key == Qt.Key_B)
label.text = 'Key B was pressed'
else if (event.key == Qt.Key_C)
label.text = 'Key C was pressed'
}
}

The pic1 is the result form doc. And the pic2 is the result of my running which i just copy the code from doc and run it.


pic1
https://i.stack.imgur.com/6sQGy.png

pic2
https://i.stack.imgur.com/hiZeP.png



Is it a bug? Why the result are different?

**The doc said**:

We want the first MyWidget object to have the focus, so we set its focus property to true. However, by running the code, we can confirm that the second widget receives the focus.

Looking at both MyWidget and window code, the problem is evident - there are three types that set the focus property to true. The two MyWidgets set the focus to true and the window component also sets the focus. Ultimately, only one type can have keyboard focus, and the system has to decide which type receives the focus. When the second MyWidget is created, it receives the focus because it is the last type to set its focus property to true.

**My question**:

1.Why the result are different?In my result the first widget receives the focus.


2.Also, what is the meaning of"because it is the last type to set its focus property to true"in doc?

**The doc you can get from here!**
http://doc.qt.io/qt-5/qtquick-input-focus.html

[wysota]

Your result is what I'd expect to happen. Maybe the docs are outdated. You should be using FocusScope to work around this ambiguity.


Ad 2. QML evaulates elements in a top-down manner so the bottom-most element will be the last element to try and set its focus property to true. Since only one item can have focus, the docs claim it will be switching from one element to the next as it grabs focus.

[mrmuto2]

Thank you for your answer. As the result is different from the docs. The sentence "because it is the last type to set its focus property to true" is wrong, right? It should be "The first type to set its focus property to true""

[wysota]

The sentence "because it is the last type to set its focus property to true" is wrong, right?
I would assume so.


It should be "The first type to set its focus property to true""
Not quite. It might be that it is so because it is the top-most document of a hierarchy that sets the conflicting focus. Or it might be something different :)

[mrmuto2]

Thank you very much