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
> -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
> -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-bounc
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 fir
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 a
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 ma
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.
__
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.
___
In
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
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 Load
On Wed, Jan 15, 2014 at 6:26 AM, 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
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
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.
___
13 matches
Mail list logo
