Hello again,
FYI there is no such thing as Qt::SmoothScale in QPainter::drawImage or
QPainter::drawPixmap so I ended up with something like:
QPixmap pixscaled(QSize(scaleX, scaleY));
if(scaleX pix.width() || scaleY pix.height()) {
pixscaled.fill(Qt::transparent);
Hello,
I’m trying to update Qt 5.5 for all my project and I’m having very bad behavior
of StackView.
What has been changed on StackView that may break compatibility ?
All my app has a center item that it’s a StackView and I push/pop element on
that. But It doesn’t work anymore.
I didn’t use any
Hi there,
I would like to embed an NSView wrapped in a QMacCocoaViewContainer into a
GraphicsView.
I’ve tried adding it as a QGraphicsProxyWidget, but although it shows the
widget, it doesn’t show the contents of the NSView.
Has anyone got any pointers that might help me?
TIA
Ziggy Uszkurat
I have a question regarding the Moc builder and expected source code
dependency graphs.
From http://doc.qt.io/qt-4.8/moc.html
The moc tool reads a C++ header file. If it finds one or more class
declarations that contain the Q_OBJECT macro, it produces a C++ source file
containing the
On Friday 17 July 2015 17:11:43 William Blevins wrote:
Moc builder is called on bbb,cpp which generates bbb.moc (if I understand
correctly) where bbb.cpp is define as:
#include my_qobject.h
void bbb(void) Q_OBJECT
#include bbb.moc
Q_OBJECT can only be applied to classes and structs.
On Monday 20 July 2015, maitai wrote:
Hello again,
FYI there is no such thing as Qt::SmoothScale in QPainter::drawImage or
QPainter::drawPixmap so I ended up with something like:
Yes, that I why I wrote something like. I hadn't looked up the exact
arguments.
QPixmap
One should think this is a clear warning sign. :-)
But the code worked. So problem solved. Now I am wondering if I was
over-cautious, or if there are less obvious problems. With different compilers?
Platforms? Some less known QMap/QList features, which might shuffle the objects
around? Not
On Monday 20 July 2015 16:20:50 Nuno Santos wrote:
Hi,
Is it possible to add .s/.S files into a project using qmake?
SOURCES += foo.S
I think that works.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Motorola S records? Dont they need to be parsed?
Sent:Monday, July 20, 2015 at 11:20 AM
From:Nuno Santos nunosan...@imaginando.pt
To:interest interest@qt-project.org
Subject:[Interest] How to add .s/.S assembly files to a project using qmake?
Hi,
Is it possible to add .s/.S files into a
Hi,
Is it possible to add .s/.S files into a project using qmake?
Thx,
Regards,
Nuno
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
The Qt documentation did it. :-) Where I am there are no bad developers. The
'do not copy QObject' was just an unfortunate lack of information. Together
with 'oh no, we don't have the time for a non-trivial redesign like that' I had
some convincing to do.
The point you listed below are the
From: Guido Seifert
Hi, just seen this in project's code. Worse, I have been told to do it
exactly this way in another code part.
What about:
- the QObject's parent? Is it set with setParent(other-parent()) or set to
nullptr?
- the QObject's thread? Is it guaranteed that it is the same thread
Hi Guido,
you mean they have patched qt and gave Object an assignment operator and copy
constructor?
Really?
Regards,
Gunnar
Am 20.07.2015 um 14:51 schrieb Guido Seifert warg...@gmx.de:
Hi, just seen this in project's code. Worse, I have been told to do it
exactly this way in another
I'm trying to identify if a QCamera has a flash. Ideally, I'd like this done
in QML, but there seems to be no support for it yet. So I'm making a QML type
in C++.
So in C++:
qDebug() Default: QCameraInfo::defaultCamera().deviceName()
QCameraInfo::defaultCamera().position();
camera = new
On Monday 20 July 2015 20:19:57 Jason H wrote:
Motorola S records? Don't they need to be parsed?
The subject says assembly files.
.S has been assembly source needing preprocessor and .s preprocessed
assembly since the dawn of Unix time...
--
Thiago Macieira - thiago.macieira (AT) intel.com
And the problem with PHP is that it works at all. ;-)
Wouldn't the modifications you inquire make a mess of the implicit data sharing?
Sent: Monday, July 20, 2015 at 1:02 PM
From: Gunnar Roth gunnar.r...@gmx.de
To: Guido Seifert warg...@gmx.de
Cc: interest@qt-project.org
Subject: Re:
Hi Guido,
i know quite a many bad c/c++ code that worked … for a while ;-) thats the
problem with many bad c/c++ code, that it works somehow.
Am 20.07.2015 um 18:53 schrieb Guido Seifert warg...@gmx.de:
One should think this is a clear warning sign. :-)
But the code worked. So problem
Hi Guido,
Did they patch QObject itself, or just add these routines to a descendent -
I'll assume the latter. The added routines can't be calling the QObject
ancestor routines, since that wouldn't compile. So what are the routines
doing? Just copying over their own member vars? We'll
Am 21.07.2015 um 03:33 schrieb Tony Rietwyk:
[...] We'll need to see some code to decide how bad it is.
I'd say: Whatever the code looks like now, it is bad enough not to use
it any longer. And code is not static, so it can get worse any time... :-)
The Qt docs state that copying a QObject
Hi.
I would like to get some advice.
I am making my application using QtWebKit(Qt5.4.2) on ubuntu 15.04.
20 of QWebview is running at the same time. and they all render same
website in the main thread.
the website rendered is updating an image every single second and has some
animated effects.
hi,
i wonder why you just don't store QObject* in the lists?
moving from objects to pointers should be just fleißarbeit ;)
alex
Am Mon, 20 Jul 2015 22:18:50 +0200
schrieb Jason H jh...@gmx.com:
And the problem with PHP is that it works at all. ;-)
Wouldn't the modifications you inquire
21 matches
Mail list logo
