[Interest] iOS - Slide View Issue with Qt-5.5.1
Hi, This is not reproducible on simulator but only on iPad Air. When a Qt-widget app, i.e. textedit example with added storyboard to be seen in Slide View, is started, it works fine and appears in the small 30% window properly. However, when rotating the device, the app fails to appear with messages like below: QIOSContext failed to make complete framebuffer object (GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT) QIOSBackingStore: makeCurrent() failed The messages also appear in this bug report: https://bugreports.qt.io/browse/QTBUG-40034 Any thoughts, suggestions. Thank you. Kind regards, Robert ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] Why is QtQuick TreeView in QT 5.5.0/5.5.1rc not supported by Qt Quick Designer/Editor?
Hi, only a small question. I wanted to give QT 5.5.0 a try, and started a new QTQuick Project in QTCreator. I Open the MainForm.ui.qml in the Designer, and would like to play with the TreeView but its not available. QTCreator created the MainForm.ui.qml file when I created the project. It starts with: import QtQuick 2.5 import QtQuick.Controls 1.4 import QtQuick.Dialogs 1.2 ... So all should be here. In the doc Its mentioned as part of QT 5.5.0. I use Linux + qt open source. Is this a bug which will be fixed in 5.5.1 or is there some workaround? I did a small test with QT 5.5.1 rc by installing qt-opensource-linux-x64-5.5.1_190.run ... but its the same If I add TreeView {} in the qml file and click on "Design" in QT creator I get an error: This QML file contains features which are not supported by Qt Quick Designer. Line: 88: Unknown component.(M300) .. and in the editor "TreeView" has a red underline. Thanks for a small hint. Anton ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] DNS-SD/mDNS under Windows with Qt5
Does Qt5 under Windows have some kind of support for DNS-SD/mDNS (zero-config implemented by Bonjour and Avahi)? Or if not, does anybody know of a Qt-specific implementation? I can try to implement the Windows Bonjour SDK in my Qt application, but I'd rather not re-invent if it's already been done. ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] qmake findmocs randomly skips header files (about 1 in 1000 times)
Hello, We have a software project which consists of roughly 50 QT components, each with their own .pro file. On our continuous build server we run qmake on all of them after every commit. About 1 in 20 builds we have a random linking error due to not finding the metaobject related code for some (everytime different) class. Rerunning the build without changing anything fixes it. I traced this problem a bit and found these things: => The bad .vcxproj file is missing the necessary pre-build steps for generating the MOC objects for a random class. The .pro file clearly lists the header file, the header file does have the Q_OBJECT macro and the class does subclass QObject as first superclass. => I captured level-2 debug info from all qmake executions and found the "findMocs" step just randomly skips a file, while it is listed correctly in the HEADERS variable under "Dumping all variables". Good example output of qmake -d -d: ... DEBUG 2: findMocs: fileA.h DEBUG 2: Mocgen: fileA.h:29 Found MOC symbol Q_OBJECT DEBUG 2: findMocs: fileB.h DEBUG 2: Mocgen: fileB.h:36 Found MOC symbol Q_OBJECT DEBUG 2: findMocs: fileC.h DEBUG 2: Mocgen: fileC.h:27 Found MOC symbol Q_OBJECT ... DEBUG 1: HEADERS === fileA.h :: fileB.h :: fileC.h ... Bad example output of qmake -d -d (without any changes to the relevant files): ... DEBUG 2: findMocs: fileA.h DEBUG 2: Mocgen: fileA.h:29 Found MOC symbol Q_OBJECT DEBUG 2: findMocs: fileC.h DEBUG 2: Mocgen: fileC.h:27 Found MOC symbol Q_OBJECT ... DEBUG 1: HEADERS === fileA.h :: fileB.h :: fileC.h ... So, this is about 1 in 1000 (= 50 .pro files * 20 builds) qmake invocations where a random file is skipped. Any idea why this might happen or how I could investigate further what the rootcause might be? Googling doesn't turn up anything usefull, only advice to people who forget to rerun qmake after making a change that requires it. In our case this irrelevant, because we rerun qmake every single time. For completeness, we are using QT 4.8.6, which has qmake version 2.01a Kind regards, Pieter-Jan Busschaert ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest