Hi all, thanks for the help so far. I've decided to go with just the wayland-egl platform, as that is what is suggested by the Qt docs as being the ideal target platform. So this is Ubuntu 22.04 LTS, with the application built against Qt 6.5.3, attempting to use the wayalnd-egl platform. I've modified my application so that it packages the correct files, afaik. However i when i run my application i still run into problems. BUT if I specify the platform via adding the "-platform wayland-egl" or by exporting the QT_QPA_PLATFORM=wayland-egl My app starts as expected. However neither of these represent an ideal or long term solution :( Below is the log of attempting to start my app with no args, or special QPA platform setting james@Ubuntu22:~/Perforce/release.2.3/studio/platforms/linux/_builds/Debug/x86_64$ ./MyApp qt.core.plugin.factoryloader: checking directory path "/home/ProjectS/Perforce/release.2.3/studio/platforms/linux/_builds/Debug/x86_64/Qt/platforms" ... qt.core.plugin.factoryloader: looking at "/home/ProjectS/Perforce/release.2.3/studio/platforms/linux/_builds/Debug/x86_64/Qt/platforms/libqwayland-egl.so" qt.core.plugin.loader: Found metadata in lib /home/ProjectS/Perforce/release.2.3/studio/platforms/linux/_builds/Debug/x86_64/Qt/platforms/libqwayland-egl.so, metadata= { "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3", "MetaData": { "Keys": [ "wayland-egl" ] }, "archlevel": 1, "className": "QWaylandEglPlatformIntegrationPlugin", "debug": false, "version": 394496 } qt.core.plugin.factoryloader: Got keys from plugin meta data QList("wayland-egl") qt.core.plugin.factoryloader: checking directory path "/home/ProjectS/Perforce/release.2.3/studio/platforms/linux/_builds/Debug/x86_64/platforms" ... qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in "" qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in "" This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: wayland-egl. Aborted (core dumped) Looking at this log it looks like the qt.core.plugin.factoryloader is able to see the wayland-egl.so, but for some reason the qt.qpa.plugin is unable to find or load the wayland-egl platform?? Why isnt my application loading correctly using the wayland-egl platform as is? What is the recommended way to tell package your application which platform to use? I assume it is just putting the "libqwayland-egl.so" in the right location. which for me is the Qt/platforms location. I did look into maybe using the qt.conf file to try and specify the platform, but it doesn't appear to have any options for this either :( The fact this works when i specify the platform to use, indicates that most things are in place, I'm just stumped as to why it wont use the wayland-egl by default!!

KDAB's KDDockWidget has plans for Qt Quick support though. @colourdelete, per github.com/KDAB/KDDockWidgets/discussions/652#discussioncomment-14096746, is it even usable outside C++?

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?

这是对应主题下的帖子

@RokeJulianLockhart Sorry I do not understand what you have written. My link is to the 3rd screenshot down in the first post in this thread, scroll up. That has an "Ask a question" item shown. I get that, for example in this topic where we are now. The Topic Tools menu at top with "Ask as question" as its last item. That's all I can say.