Hi, I have a problem using QML Profiler with Qt5-Beta1 based programs. I use a
QPA based architecture on a Arm board and will try to connect the QML Profiler
with a Qt Creator 2.5.2. Is it possible? How can I do it? Do I hav do use
another Qt Creator?
Thanks.
Torsten
With best regards,
Some ways to do this:
1) If you can connect to the arm board via network, then
* Start you application with -qmljsdebugger=port:port number
* From QtCreator, connect to the applicationvia Attach to QML Profiler and
specify the IP and the above port
2) You can use the standalone profiler in
On 10/18/2012 07:53 AM, Uwe Rathmann wrote:
On Wed, 17 Oct 2012 16:47:00 +0200, Samuel Rødal wrote:
Seems to me to be the best compromise to avoid completely breaking too
much existing code.
I don't agree - it is going to break many applications doing graphics and
PDF export for a micro
According to git grep Qt 4 has 47 semi-public exported qt_platform functions
offering platform-spesific functionality. Most platform code is now in plugins
and can no longer export symbols. We need a plan for dealing with these in Qt 5.
After a brief investigation these fall into several
On Oct 16, 2012, at 10:06 PM, Uwe Rathmann uwe.rathm...@tigertal.de wrote:
We are using QWS ( we don't even have X11 for the Carmine chip ) so this
is no problem - but by QWindow you mean Qt5 ?
Yes. I can't help you with QWS, sorry.
Morten
___
On Thursday 18 October 2012 09:59:45 Samuel Rødal wrote:
In summary (or TL;DR), my new proposal would be to just make
QPainter::NonCosmeticDefaultPen work as advertised, and have it be set
by default when high-dpi mode is enabled. This way there would be
minimal breakage of existing code.
Maybe as a best effort we could introduce a different render hint,
asking QPainter to treat cosmetic pens as geometric, would be a better
solution for Morten's high-dpi use case. Then it would be opt-in instead
of opt-out, and no existing applications would be affected. Turning on
On 10/18/2012 11:08 AM, Bache-Wiig Jens wrote:
Maybe as a best effort we could introduce a different render hint,
asking QPainter to treat cosmetic pens as geometric, would be a better
solution for Morten's high-dpi use case. Then it would be opt-in instead
of opt-out, and no existing
[changed the subject to get some attention ... from a quick survey i
don't have the impression that many people grasp that this thread is
very much relevant for them.]
On Thu, Oct 11, 2012 at 04:11:10PM -0700, Thiago Macieira wrote:
On quinta-feira, 11 de outubro de 2012 21.16.56, Oswald
From: Oswald Buddenhagen oswald.buddenha...@digia.com
Subject: [Development] renaming qmake for everyone (was: Re: Co-installation
library naming rules=)
[changed the subject to get some attention ... from a quick survey i
don't have the impression that many people grasp that this thread is
On Thursday, October 11, 2012 04:11:10 PM Thiago Macieira wrote:
On quinta-feira, 11 de outubro de 2012 21.16.56, Oswald Buddenhagen wrote:
On Thu, Oct 11, 2012 at 11:56:44AM -0700, Thiago Macieira wrote:
Considering all the changes I am proposing do NOT harm any of the
people that build
After all of my patches are integrated, here are the changes that will happen:
- bin:
The following tools have been renamed:
qmake - qmake5
moc - moc5
uic - uic5
rcc - rcc5
qdbusxml2cpp - qdbusxml2cpp5
On Mon, Oct 15, 2012 at 11:00 PM, Thiago Macieira thiago.macie...@intel.com
wrote:
On segunda-feira, 15 de outubro de 2012 14.53.39, Olivier Goffart wrote:
Is there any value in keeping a signal that is:
- Only emitted after the program destabilises, and
- Not even guaranteed to be
On Thursday 18 October 2012 23:40:21 Sze Howe Koh wrote:
Ok, I just had a look at the source code to study how to remove the signal.
It looks like the QThread::terminated() signal is only ever emitted from
QThreadPrivate::finish(), if the appropriate flag is set (for both Unix and
Win
On Tue, 16 Oct 2012, Thiago Macieira wrote:
On terça-feira, 16 de outubro de 2012 15.25.40, Jon Trulson wrote:
However, compiling qtwayland fails with many errors - errors that
imply qtwayland cannot work with the wayland installed on the rpi.
Probably. Upgrade your Wayland to 0.95 at least.
On 18.10.2012, at 16:30, BRM wrote:
From: Oswald Buddenhagen
oswald.buddenha...@digia.commailto:oswald.buddenha...@digia.com
Subject: [Development] renaming qmake for everyone (was: Re: Co-installation
library naming rules=)
[changed the subject to get some attention ... from a quick survey
On 12.10.2012, at 01:11, Thiago Macieira wrote:
On quinta-feira, 11 de outubro de 2012 21.16.56, Oswald Buddenhagen wrote:
On Thu, Oct 11, 2012 at 11:56:44AM -0700, Thiago Macieira wrote:
Considering all the changes I am proposing do NOT harm any of the
people that build from sources,
they *do*
On 18 October 2012 16:30, Thiago Macieira thiago.macie...@intel.com wrote:
The following tools require more information:
qdoc: not renamed because the Qt 4 version was called qdoc3
qhelpgenerator, qcollectiongenerator, qhelpconverter: they apparently
keep backwards
Any chance you guys can configure your email clients to do proper quoting on
mailing lists? And please send plain text only.
I'm entirely ignoring the message below because it's mangling what I said with
what Ossi said, BRM said and Eike added.
On quinta-feira, 18 de outubro de 2012 16.14.37,
On 2012-10-18, Giuseppe D'Angelo dange...@gmail.com wrote:
The following are user applications and they have not and will not be
renamed:
qdbus
qdbusviewer
assistant
designer
linguist
creator
pixeltool
I would remove creator from
On quinta-feira, 18 de outubro de 2012 18.23.38, Olivier Goffart wrote:
I agree with Ossi on this matter.
I will add that i don't like to rename qmake to qmake5 because:
One runs firefox, not firefox15.
Firefox is an end-user application. You upgrade it and you don't keep the
older
On Oct 18, 2012, at 5:30 PM, Thiago Macieira wrote:
After all of my patches are integrated, here are the changes that will happen:
- bin:
The following tools have been renamed:
qmake - qmake5
moc - moc5
uic - uic5
rcc - rcc5
qdbusxml2cpp - qdbusxml2cpp5
qdbuscpp2xml - qdbuscpp2xml5
lconvert
On 18 October 2012 17:23, Olivier Goffart oliv...@woboq.com wrote:
Take the most recent example of python. They did not rename the executable.
Some distribution renamed the new one to python3, some other (archlinux)
renamed the old one python2.
Let the distributions solve the distributor's
On quinta-feira, 18 de outubro de 2012 17.47.16, Giuseppe D'Angelo wrote:
The following are user applications and they have not and will not be
renamed:
qdbus
qdbusviewer
assistant
designer
linguist
creator
pixeltool
I
On 18.10.2012, at 18:47, Giuseppe D'Angelo wrote:
On 18 October 2012 16:30, Thiago Macieira thiago.macie...@intel.com wrote:
The following tools require more information:
qdoc: not renamed because the Qt 4 version was called qdoc3
qhelpgenerator, qcollectiongenerator,
Reposting after setting some plain text flags in the mail client, in the hope
of better readability for Thiago.
On 18.10.2012, at 16:30, BRM wrote:
From: Oswald Buddenhagen oswald.buddenha...@digia.com
Subject: [Development] renaming qmake for everyone (was: Re: Co-installation
library
On quinta-feira, 18 de outubro de 2012 18.05.31, Ziller Eike wrote:
I'd throw Mac out of sentences that have Linux in them in this discussion:
There are no Mac distributions/distributors that package Qt
There's MacPorts.
On Mac, Qt will either be self-compiled (you are on your own which is
On Thu, Oct 18, 2012 at 05:47:16PM +0100, Giuseppe D'Angelo wrote:
On 18 October 2012 16:30, Thiago Macieira thiago.macie...@intel.com wrote:
The following tools require more information:
qdoc: not renamed because the Qt 4 version was called qdoc3
qhelpgenerator,
Bump.
What's going on with this important issue?
-Am I being ignored (in which case, I should have used a pseudonym to
present my argument)?
-Has discussion halted because of a lack of consensus (in which case,
I present to you the following image: http://bayimg.com/eAEhDAaEE )?
-Am I being
On Thu, Oct 18, 2012 at 08:30:03AM -0700, Thiago Macieira wrote:
lconvert- lconvert5
lrelease- lrelease5
lupdate - lupdate5
Sorry, I don't get the joke.
Andre'
___
Development mailing list
Development@qt-project.org
On sexta-feira, 19 de outubro de 2012 01.03.29, André Pönitz wrote:
On Thu, Oct 18, 2012 at 08:30:03AM -0700, Thiago Macieira wrote:
lconvert- lconvert5
lrelease- lrelease5
lupdate - lupdate5
Sorry, I don't get the joke.
Because it was no joke. It's serious.
On Fri, Oct 19, 2012 at 2:06 AM, Jon Trulson j...@radscan.com wrote:
On Tue, 16 Oct 2012, Thiago Macieira wrote:
On terça-feira, 16 de outubro de 2012 15.25.40, Jon Trulson wrote:
However, compiling qtwayland fails with many errors - errors that
imply qtwayland cannot work with the wayland
On quinta-feira, 18 de outubro de 2012 08.30.03, Thiago Macieira wrote:
xmlpatterns - xmlpatterns5
xmlpatternsvalidator - xmlpatternsvalidator5
I've changed my mind on those two and dropped the patches that dealt with
them.
Those two are end-user applications and retain full
On Thu, Oct 18, 2012 at 10:16:37AM -0700, Thiago Macieira wrote:
I would remove creator from this list as it's a different product
and comes with its own versioning and release cycle -- are all of
those 100% compatible with Qt 4? (First thing that comes to mind is
that designer loads
On Thu, Oct 18, 2012 at 04:10:16PM -0700, Thiago Macieira wrote:
On sexta-feira, 19 de outubro de 2012 01.03.29, André Pönitz wrote:
On Thu, Oct 18, 2012 at 08:30:03AM -0700, Thiago Macieira wrote:
lconvert- lconvert5
lrelease- lrelease5
lupdate - lupdate5
On 19/10/12 01:30, Thiago Macieira wrote:
After all of my patches are integrated, here are the changes that will happen:
- bin:
The following tools have been renamed:
So... You just don't care about the calls from myself and others to
leave the names alone instead install newly-named
On sexta-feira, 19 de outubro de 2012 01.44.18, André Pönitz wrote:
Creator needs *some* solution of some kind so that its Designer component
can work for Qt 4 and Qt 5.
Why? _You_ call Widgets done. Why do you suddenly care how people
handle them?
Done still means people can design new
On sexta-feira, 19 de outubro de 2012 01.57.16, André Pönitz wrote:
On Thu, Oct 18, 2012 at 04:10:16PM -0700, Thiago Macieira wrote:
On sexta-feira, 19 de outubro de 2012 01.03.29, André Pönitz wrote:
On Thu, Oct 18, 2012 at 08:30:03AM -0700, Thiago Macieira wrote:
lconvert
On 19/10/12 02:23, Olivier Goffart wrote:
On Thursday 18 October 2012 08:30:03 Thiago Macieira wrote:
After all of my patches are integrated, here are the changes that will
happen:
- bin:
The following tools have been renamed:
qmake - qmake5
moc - moc5
uic
On sexta-feira, 19 de outubro de 2012 10.17.39, Lincoln Ramsay wrote:
On 19/10/12 01:30, Thiago Macieira wrote:
After all of my patches are integrated, here are the changes that will
happen:
- bin:
The following tools have been renamed:
So... You just don't care about the calls from
Whoops that third one was a typo, should have read I am instead of Am I.
I am clearly not being listened to :-P (and I should have used a
pseudonym to trick your inferior brain(s)). You should not associate
an argument with the person presenting it (even though most do). It is
fallacious.
So can
tl;dr:
Open Project
Closed Security
The officially endorsed method for reporting security issues for Qt is
to send them to security at qt-project.org , which is a private mailing
list. I have a problem with that.
Experience has shown that 'security through obscurity' does not work.
42 matches
Mail list logo
