You're welcome! Thank you for sharing your journey and your solution. Here are some additional tidbits that might be of interest to you: Anchor default values Items are always placed at their parent's top-left by default. So, you can omit these lines and still get the same result: anchors.top: parent.top anchors.left: parent.left Having said that, you can also keep them for clarity. Label vs. Text Displaying text inside a coloured rectangle is a very common requirement. You can simplify your code by using Label instead (https://doc.qt.io/qt-6/qml-qtquick-controls-label.html ). Add import QtQuick.Controls.Basic and try the following: Label { id: name background: Rectangle { color: "blue" } text: myContactInfo.name font.pointSize: 30 } Label { id: address anchors.top: name.bottom background: Rectangle { color: "green" } text: myContactInfo.address font.pointSize: 15 } Note: One difference is that Label might change your font colour based on your OS settings (e.g. dark mode) Positioners vs. Anchors See https://doc.qt.io/qt-6/qtquick-positioning-layouts.html -- instead of anchoring your 2nd label to the 1st label, you could put them inside a Column: Column { // Quiz (open-book): What is the width and height of this Column? Label { id: name background: Rectangle { color: "blue" } text: myContactInfo.name font.pointSize: 30 } Label { id: address background: Rectangle { color: "green" } text: myContactInfo.address font.pointSize: 15 } }

Have a good time, regardless of what your next adventure will be!

Try another pc, maybe the graphics card driver has a problem with it.

Hi, I have developed QML application having two Inputbox and one button with mentioning the ids of each component. When I recording and verifying with Squish tool I am not getting type(waitForObject(..), "") function/API in my script. I want to have text/caption of the button and input text of the both input box from my QML application. The same thing i am getting by running the addressbook example exe with Squish tool as following. startApplication("Addressbook") mouseClick(waitForObjectItem(names.address_Book_Unnamed_Menubar, "File")) mouseClick(waitForObjectItem(names.file_MenuItem, "New")) mouseClick(waitForObject(names.add_ToolbarItem)) type(waitForObject(names.address_Book_Add_Forename_Edit), "sumit") mouseClick(waitForObject(names.address_Book_Add_Surname_Edit), 42, 14, MouseButton.PrimaryButton) type(waitForObject(names.address_Book_Add_Surname_Edit), "Dine") mouseClick(waitForObject(names.address_Book_Add_Email_Edit), 37, 15, MouseButton.PrimaryButton) type(waitForObject(names.address_Book_Add_Email_Edit), "djihf") mouseClick(waitForObject(names.address_Book_Add_Phone_Edit), 29, 5, MouseButton.PrimaryButton) type(waitForObject(names.address_Book_Add_Phone_Edit), "1233") clickButton(waitForObject(names.address_Book_Add_OK_Button)) What need to do further ? Is there anything require to add or missed either on Qt side or Squish side ? Please help.

Hey @Carditus, We have released our Certification Testing Platform with the first test. Read more here: https://www.qt.io/qt-certifications.

Adding to this, I know that the thread isn't causing the jitter now, as it consistently logs 16'666'667 to 16'666'668. This is a rendering issue: I get smooth gameplay when the lag phases haven't kicked in using my 3rd approach, but when they finally occur, it isn't visually pleasing. -The second approach is more consistent overall, but still not smooth: There's noticeable jitter due to the timeout drops but it's far less than the 1st approach. However, the jitter remains throughout the entire experience. There's downsides to both, but I prefer smoother gameplay, which makes me prefer the 3rd approach overall. I just don't understand how to keep the thread light, while running every 16 seconds down to the ms without jarring hiccups. I've tried using msleep, but it's very course, which doesn't help my issue. Again, the 2nd approach would be ideal if the timeout never got called so early. Maybe there is a method to prevent that?

这是对应主题下的帖子

@JonB said in Hitchhiker's Visual Guide to the Qt Forum: @RokeJulianLockhart I am indeed a moderator, so that may make a difference. I do not know what "Ask as question" does! :) It turns a "normal post" to a question that can be marked as solved. This can be useful for example when an old imported topic still gets activity but was marked solved the old way.