> Am 12.12.2014 um 07:59 schrieb Igor Mironchik :
>
> ...
> Look at the explanation of "If this property is false", is it correct or
> "false" should be "true"?
Yes, it's not true that this is false. Replace false by true and (or?)
re-evaluate my previous statement.
;)
Cheers,
Oliver
Hi. In documentation for invertedAppearance property of QProgressBar said:
"This property holds whether or not a progress bar shows its progress
inverted.
If this property is false, the progress bar grows in the other direction
(e.g. from right to left). By default, the progress bar is not in
On Thursday 11 December 2014 21:33:35 René J.V. Bertin wrote:
> But how do I turn exceptions back on in xmlpatterns.pro? Do I add
> -UQT_NO_EXCEPTIONS to the compiler flags (and cross thumbs), or is there a
> better way?
CONFIG += exceptions
--
Thiago Macieira - thiago.macieira (AT) intel.com
S
On Thursday December 11 2014 10:52:00 Thiago Macieira wrote:
> Edit configure so it won't disable qtxmlpatterns. Then edit
> src/xmlpatterns/xmlpatterns.pro to turn exceptions back on.
So that works ... until xmlpatterns/utils/qpatternistlocale_p.h detects
QT_NO_EXCEPTIONS which gets set in qc
On Thursday December 11 2014 10:52:00 Thiago Macieira wrote:
> src/xmlpatterns/xmlpatterns.pro to turn exceptions back on.
Doh...
DEFINES-=QT_NO_EXCEPTIONS should do the trick (with that, no sign of anything
"exception" in src/xmlpatterns/Makefile)
R.
___
On Thursday December 11 2014 10:52:00 Thiago Macieira wrote:
> Edit configure so it won't disable qtxmlpatterns. Then edit
> src/xmlpatterns/xmlpatterns.pro to turn exceptions back on.
The configure edit seems easy enough: just change the block
if [ "$CFG_XMLPATTERNS" = "yes" -a "$CFG_EXCEPTION
On Thursday 11 December 2014 19:31:32 René J.V. Bertin wrote:
> On Thursday December 11 2014 09:49:35 Thiago Macieira wrote:
> > Use Qt 5. It's done there.
>
> How funny
Edit configure so it won't disable qtxmlpatterns. Then edit
src/xmlpatterns/xmlpatterns.pro to turn exceptions back on.
-
On Thursday December 11 2014 09:49:35 Thiago Macieira wrote:
> Use Qt 5. It's done there.
How funny
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
On Thursday 11 December 2014 18:44:38 René J.V. Bertin wrote:
> On Wednesday December 10 2014 18:03:15 Thiago Macieira wrote:
> > > That's what I saw after reading up a bit more on the topic. But if
> > > QtXmlPatterns doesn't build without them, I'm stuck with -fexceptions as
> > > KDE uses QtXmlP
On Wednesday December 10 2014 18:03:15 Thiago Macieira wrote:
> > That's what I saw after reading up a bit more on the topic. But if
> > QtXmlPatterns doesn't build without them, I'm stuck with -fexceptions as
> > KDE uses QtXmlPatterns ...
>
> Try and see. I think xmlpatterns.pro turns it back
On Thursday 11 December 2014 15:29:58 Rainer Wiesenfarth wrote:
> (qorderedmutexlocker_p.h:83)
> ==26941==by 0x6E0F677: QObject::connect(QObject const*, char const*,
> QObject const*,
> char const*, Qt::ConnectionType) (qobject.cpp:2713)
> ==26941==[...]
>
A quick follow up question to this thread I am using searchAndLock() on my
first picture. But on the 2nd picture I just call capture again. It again goes
through a focus seeking operation. Is there a way to use the same focus
paramters as the previous photo? Even if I set
camera.focus.foc
Thanks Yoann, I was able to kludge something together that works well enough. I would have loved to be able to more simple way. One of the things I found in my kludging, was that "ready" sometimes comes back faster than the capture handler, and other times it does not. This was the main source of m
I am not yet very familiar with helgrind, but if I use it on my application
I get a couple of messages like this:
==26941==
==26941==
==26941== Thread #1: lock order "0x723FA50 before 0x723FA90" violated
==26941==
==26941== Observe
On 11 Dec 2014, at 15:15, Jason H mailto:jh...@gmx.com>> wrote:
Which ready are we talking about? The flash ready or the camera ready? I don't
mind adding an onReadyChanged, but it is not clear where I should add it.
I meant the Camera.imageCapture.ready property.
_
Which ready are we talking about? The flash ready or the camera ready? I don't mind adding an onReadyChanged, but it is not clear where I should add it.
Thanks.
Sent: Thursday, December 11, 2014 at 9:03 AM
From: "Lopes Yoann"
To: "Jason H'"
Cc: "interest@qt-project.org"
Subject: Re: [In
On 11 Dec 2014, at 13:02, Jason H' mailto:jh...@gmx.com>> wrote:
It's not so much that I need sub-second captures. It's that i need to reliably
have my requests serviced. Currently if I do the trivial case that should be
possible according to the docs, the 2nd request fails more than it succeed.
> Am 11.12.2014 um 12:17 schrieb Alejandro Exojo :
>
> ...I can't say for iOS, but on Android almost all
> applications that I use seem to use their own kind of controls. There is very
> little consistency, and users seem to not care.
Oh, users do care, they do. It's just that those users are
It's not so much that I need sub-second captures. It's that i need to reliably have my requests serviced. Currently if I do the trivial case that should be possible according to the docs, the 2nd request fails more than it succeed. If I make the request in the onImageCaptured hand
On 10 Dec 2014, at 21:33, Jason H wrote:
>
> Per http://qt-project.org/doc/qt-5/qml-qtmultimedia-cameracapture.html
> "It's permissible to call capture() while the camera is active regardless of
> the ready property value. If camera is not ready to capture image
> immediately, the capture reque
Hi,
Note: a 'Flat light' style caveat is that according to
http://www.qt.io/qt5-4/
it's available under commercial license only (so you might be looking for it
in the wrong place)
Best regards,
Attila
On 12/11/2014 5:24 AM, Jason H' wrote:
+1 this. I want info on the new flat style as well.
El Wednesday 10 December 2014, Daniel França escribió:
> The just launched Qt5.4 come with a "flat light" style for Qt Quick
> Controls :D
> It seems it'll help to achieve what I want, but I can't find any
> documentation about those pre-defined styles.
>
> Every time I search for something relate
Hi,
Styling is obviously important, but at long as it's only skin-deep (ie
the full range
and feel of components is not there), it's going to lead to frustration
on the long
run. The downside of drawing/making your components (whether by the Qt team
or 3rd party devs) is that you're reimplemen
Hi
It was a missing path to dependant libraries
Thanks for the hint
Graham
From: interest-bounces+graham.labdon=avalonsciences@qt-project.org
[mailto:interest-bounces+graham.labdon=avalonsciences@qt-project.org] On
Behalf Of Tony Rietwyk
Sent: 10 December 2014 23:49
To: Interest@qt-pro
El Wednesday 10 December 2014, Graham Labdon escribió:
> Hi
> I have developed some designer plugins that are working nicely.
> Now I have created another but cannot get it to work.
> Within designer I see the following when I do Help->about Plugins -
>
> Failed Plugins
>
> C:\Qt\Qt5.3.0\5.3\m
25 matches
Mail list logo
