[Interest] Qt5.2: QtCore/private/qwineventnotifier_p.h: No such file or directory
Dear All, I just update Qt from 4.7.3 to 5.2, when build qserialdevice, below error reported: In file included from ../TSA_Data/UART/SRC/qserialdevice/abstractserialnotifier.cpp:2:0: ../TSA_Data/UART/SRC/qserialdevice/nativeserialnotifier.h:8:50: fatal error: QtCore/private/qwineventnotifier_p.h: No such file or directory #include QtCore/private/qwineventnotifier_p.h Anybody help? Thanks, VIncent. This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message. ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Qt5.2: QtCore/private/qwineventnotifier_p.h: No such file or directory
-Original Message- From: interest-bounces+kai.koehne=digia@qt-project.org [mailto:interest-bounces+kai.koehne=digia@qt-project.org] On Behalf Of Vincent Cai Sent: Wednesday, January 15, 2014 2:11 PM To: interest@qt-project.org Subject: [Interest] Qt5.2: QtCore/private/qwineventnotifier_p.h: No such file or directory Dear All, I just update Qt from 4.7.3 to 5.2, when build qserialdevice, below error reported: In file included from ../TSA_Data/UART/SRC/qserialdevice/abstractserialnotifier.cpp:2:0: ../TSA_Data/UART/SRC/qserialdevice/nativeserialnotifier.h:8:50: fatal error: QtCore/private/qwineventnotifier_p.h: No such file or directory #include QtCore/private/qwineventnotifier_p.h Anybody help? Qwineventnotifier is a public class in 5.2, so qserialdevice should rather include QtCore/qwineventnotifier.h. And it does so for me (git stable branch). Where did you get the sources from? Regards Kai ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Qt5.2: QtCore/private/qwineventnotifier_p.h: No such file or directory
-Original Message- From: Koehne Kai Sent: Wednesday, January 15, 2014 2:24 PM To: 'Vincent Cai'; interest@qt-project.org Subject: RE: [Interest] Qt5.2: QtCore/private/qwineventnotifier_p.h: No such file or directory -Original Message- From: interest-bounces+kai.koehne=digia@qt-project.org [mailto:interest-bounces+kai.koehne=digia@qt-project.org] On Behalf Of Vincent Cai Sent: Wednesday, January 15, 2014 2:11 PM To: interest@qt-project.org Subject: [Interest] Qt5.2: QtCore/private/qwineventnotifier_p.h: No such file or directory Dear All, I just update Qt from 4.7.3 to 5.2, when build qserialdevice, below error reported: In file included from ../TSA_Data/UART/SRC/qserialdevice/abstractserialnotifier.cpp:2:0: ../TSA_Data/UART/SRC/qserialdevice/nativeserialnotifier.h:8:50: fatal error: QtCore/private/qwineventnotifier_p.h: No such file or directory #include QtCore/private/qwineventnotifier_p.h Anybody help? Qwineventnotifier is a public class in 5.2, so qserialdevice should rather include QtCore/qwineventnotifier.h. And it does so for me (git stable branch). Where did you get the sources from? Sorry, I checked the sources in qserialport (https://qt.gitorious.org/qt/qtserialport), not qserialdevice. I understand qserialport is actually a continuation of qtserialdevice repo: http://qt-project.org/wiki/QtSerialPort . So you might consider switching ... Regards Kai ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] Caching of compiled/initialized qml code to disk possible?
Hi all, I have an application written with Qt 5.2 in C++ and QtQuick2, running on a low-end ARM device. I use the Loader item to select between various screens in the application (I've currently got 6 screens or so). This way I can limit the amount of active bindings at a given time, etc. The first time I enter a new screen, there is a very noticeable delay (1-2 seconds), as the new items are compiled. The next time I enter the same screen, the delay is much shorter. So I guess some things have been cached in memory. Would it be possible to cache this on disk, to prevent this from happening every single time the application is started? I'm asking for something pretty similar to Python's .pyc files. Is it possible, or would it be possible in some future version of Qt? Cheers, Ola ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] qdialog behaviour and repaint issue on embedded
hello, i’m in the process of “porting/adjusting” a pre-Qt Quick UI (just C++) from desktop to an embedded platform. the app had started on Qt 4.8.x and has now moved to Qt 5.0.2, which is the Qt version used by the target linux embedded platform. i’m still trying to absorb the notion of QPA’s and their reliance to implementation plugins, along with any documentation i could find on how the paint system works in Qt 5. i’m currently using the eglfs plugin for my needs. the problem is that whenever a QDialog based widget pops up (e.g. .show or .exec methods) in my app and after it gets dismissed, the background widget (typically a QMainWindow) does not get repainted, i get just a grayed out screen with no containing widgets (QPushButton’s, etc) visible. i tried to call refresh to no avail, but repaint/resize calls *do* redraw the interface, but thereafter no other repainting takes place, although the underlying widgets receive mouse events (i can tell from the app’s log). changing the derived the dialog boxes to inherit from QFrame instead of QDialog works (as in no repaint issues), although app-specific functionality is somewhat crippled. so, to summarize my initial questions are: 1] what is a surface in Qt 5? how does it relate to the QSurface class? 2] is the single surface/full screen of eglfs anywhere documented? is it only on embedded? (as you might understand i do not fully grasp the relationships between those elements) 3] QWindow inherits from QSurface. I understand the need for QWindow, although i’d expect QWidgets like QDialog to derive from it as well. Is it used privately or through composition? If not, how are QWidget based windows actually painted? any ideas/suggestions/pointers (to doc) would be greatly appreciated. ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] Detach widget from QDockWidget
Hi, In my app, I have tabs in the main window. A dock widget allows setting display options for the current tab. Since each tab may have a different dock widget options layout, I was considering the following: - Each tab keeps a QWidget options dialog on its own - When a tab is selected, the main window sets this widget in the dock widget. However, it seems that once QDockWidget::setWidget is used, the given widget cannot be detached from it. So it seems I have to recreate a widget every time, and reconfigure it. Any simple idea? Is it possible to detach from a QDockWidget? Thanks! Etienne ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] QColor::lighter()
Hi. Is it correct that QColor( Qt::black ).lighter() returns the same black color? For this line of code: qDebug() QColor( Qt::black ) QColor( Qt::black ).lighter(); I receive next output: QColor(ARGB 1, 0, 0, 0) QColor(ARGB 1, 0, 0, 0) -- Best Regards, Igor Mironchik. ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] QColor::lighter()
On 1/15/2014 1:38 PM, Igor Mironchik wrote: Is it correct that QColor( Qt::black ).lighter() returns the same black color? Sure. lighter() multiplies the values of the color by the scale factor passed into lighter(). It's a gain, not a bias. ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] QColor::lighter()
Igor, Paul is correct. In the case of black or similarly dark colors, I would suggest making a function that identifies how dark your color is beforehand(such as checking if all 3 RGB values fall beneath a threshold considering RGB(1,1,1) etc... are still hard to see visually ) and then increasing the lightness factor accordingly. That should ensure that the darker colors get lightened more so you can visually tell the difference easier. On Wed, Jan 15, 2014 at 12:41 PM, Paul Miller stel...@gmail.com wrote: On 1/15/2014 1:38 PM, Igor Mironchik wrote: Is it correct that QColor( Qt::black ).lighter() returns the same black color? Sure. lighter() multiplies the values of the color by the scale factor passed into lighter(). It's a gain, not a bias. ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Caching of compiled/initialized qml code to disk possible?
Hi, We are currently working on a project where we cache all screens on start-up, by using Qt.createComponent(url). By this the major components are parsed and cached on start-up. It has also a second benefit, it verifies your components on syntax error on start-up. For my knowledge the Loader element will try to load the component later and will hit the cache (as the URL is the same). Actually we go even a step further to create a large registry of all application screens so we can call the screens by the registered name and not the component url. / jryannel On 15.01.14 15:26, Ola Røer Thorsen wrote: Hi all, I have an application written with Qt 5.2 in C++ and QtQuick2, running on a low-end ARM device. I use the Loader item to select between various screens in the application (I've currently got 6 screens or so). This way I can limit the amount of active bindings at a given time, etc. The first time I enter a new screen, there is a very noticeable delay (1-2 seconds), as the new items are compiled. The next time I enter the same screen, the delay is much shorter. So I guess some things have been cached in memory. Would it be possible to cache this on disk, to prevent this from happening every single time the application is started? I'm asking for something pretty similar to Python's .pyc files. Is it possible, or would it be possible in some future version of Qt? Cheers, Ola ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Caching of compiled/initialized qml code to disk possible?
On Wed, Jan 15, 2014 at 6:26 AM, Ola Røer Thorsen o...@silentwings.no wrote: Hi all, I have an application written with Qt 5.2 in C++ and QtQuick2, running on a low-end ARM device. I use the Loader item to select between various screens in the application (I've currently got 6 screens or so). This way I can limit the amount of active bindings at a given time, etc. The first time I enter a new screen, there is a very noticeable delay (1-2 seconds), as the new items are compiled. The next time I enter the same screen, the delay is much shorter. So I guess some things have been cached in memory. Would it be possible to cache this on disk, to prevent this from happening every single time the application is started? I'm asking for something pretty similar to Python's .pyc files. Is it possible, or would it be possible in some future version of Qt? An optimization of this sort has been investigated, and while not possible now it is possible in a future version of Qt. I just don't know when that work will be done, so it might be a while. -- Alan Alpert ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Qt5.2: QtCore/private/qwineventnotifier_p.h: No such file or directory
Hi kai, Thanks for your reply. Per your suggestion, I met below compiling error: In file included from ../TSA_Data/UART/SRC/qserialdevice/abstractserialnotifier.cpp:2:0: ../TSA_Data/UART/SRC/qserialdevice/nativeserialnotifier.h:37:5: error: 'OVERLAPPED' in namespace '::' does not name a type ::OVERLAPPED o; ^ ../TSA_Data/UART/SRC/qserialdevice/nativeserialnotifier.h:38:5: error: 'DWORD' in namespace '::' does not name a type ::DWORD currentMask; ^ ../TSA_Data/UART/SRC/qserialdevice/nativeserialnotifier.h:39:5: error: 'DWORD' in namespace '::' does not name a type ::DWORD setMask; ^ the related source code: private: ::OVERLAPPED o; ::DWORD currentMask; ::DWORD setMask; How can I fix it? Thanks, VIncent. -Original Message- From: Koehne Kai [mailto:kai.koe...@digia.com] Sent: Wednesday, January 15, 2014 9:24 PM To: Vincent Cai; interest@qt-project.org Subject: RE: [Interest] Qt5.2: QtCore/private/qwineventnotifier_p.h: No such file or directory -Original Message- From: interest-bounces+kai.koehne=digia@qt-project.org [mailto:interest-bounces+kai.koehne=digia@qt-project.org] On Behalf Of Vincent Cai Sent: Wednesday, January 15, 2014 2:11 PM To: interest@qt-project.org Subject: [Interest] Qt5.2: QtCore/private/qwineventnotifier_p.h: No such file or directory Dear All, I just update Qt from 4.7.3 to 5.2, when build qserialdevice, below error reported: In file included from ../TSA_Data/UART/SRC/qserialdevice/abstractserialnotifier.cpp:2:0: ../TSA_Data/UART/SRC/qserialdevice/nativeserialnotifier.h:8:50: fatal error: QtCore/private/qwineventnotifier_p.h: No such file or directory #include QtCore/private/qwineventnotifier_p.h Anybody help? Qwineventnotifier is a public class in 5.2, so qserialdevice should rather include QtCore/qwineventnotifier.h. And it does so for me (git stable branch). Where did you get the sources from? Regards Kai This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message. ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Qt5.2: QtCore/private/qwineventnotifier_p.h: No such file or directory
On quinta-feira, 16 de janeiro de 2014 01:56:54, Vincent Cai wrote: How can I fix it? Please use QtSerialPort. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center signature.asc Description: This is a digitally signed message part. ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
