Thiago Macieira wrote:
You'll need to test with upstream Clang 3.7 and 3.8 to verify whether the
issue is fixed. Apple's random point in the release cycle plus random set of
patches Clang is not a good testbed for reporting compiler failures.
I'd agree with you if it weren't so damn difficult
On Thursday 23 July 2015 23:03:25 René J. V. Bertin wrote:
I will not take a patch that disables CRC32 due to a compiler bug in an
unsupported configuration (LTO), especially if it's already fixed in the
latest version.
But what about the fact that that those intrinsics are still used
I have this working with DirectWrite on Windows,
but it only appears to work when my app is built with debug mode.
If I build it in release mode then it does *not* work
and the text appears badly kerned.
This was all my fault.
(D'oh My release build was not using the intended dlls.)
The
On 24 July 2015 at 01:28, Thiago Macieira thiago.macie...@intel.com wrote:
On Thursday 23 July 2015 16:05:44 Guido Seifert wrote:
Op 23-7-2015 om 08:42 schreef Thiago Macieira:
Q_GADGET has existed since 4.0.
Sure, but it was undocumented API.
Not quite. It was badly documented API. I
Ok, thanks for info. I filled the bug report:
https://bugreports.qt.io/browse/QTBUG-47399
Juhani
Mike Krus mike.k...@kdab.com kirjoitti 23.7.2015 kello 13.48:
On 23/07/2015 11:26, Juhani Matilainen wrote:
Hmmm... Interesting, it seems that random texts are displayed in wrong
Hi,
Thanks for your answer. I thought like that and implemented it. But after
restoring default state, mainwindow turns small size and I have to click
fullscreen button to be a fullscreen window.
I think I have to do something to be a fullscreeen windows again after
restoring state.
On Thu,
On 07/21/2015 01:31 PM, william.croc...@analog.com wrote:
On 07/18/2015 08:02 PM, william.croc...@analog.com wrote:
I am having a text rendering problem.
What you can do in your example is
scene_font.setHintingPreference(QFont::PreferNoHinting);
It appears that one needs to use
Concerning my test Qt5 build with LTO:
How well supported/tested is doing that in out-of-source shadow build? After
using -march=core2 instead of -march=native (and thus avoiding the use of SSE4
instructions), I'm running into another issue when I execute qmake -config ltcg
immediately after
I have got the same problem. Upvoted for your issue.
On 23 July 2015 at 19:28, Juhani Matilainen juh...@theocbase.net wrote:
Ok, thanks for info. I filled the bug report:
https://bugreports.qt.io/browse/QTBUG-47399
Juhani
Mike Krus mike.k...@kdab.com kirjoitti 23.7.2015 kello 13.48:
Is the qt.io site - at least the support pages etc. - down or do I have a
problem at my side of the tube?
Best Regards / Mit freundlichen Grüßen
Rainer Wiesenfarth
--
Software Engineer | Trimble Geospatial
Rotebühlstraße 81 | 70178 Stuttgart | Germany
Office +49 711 22881 0 | Fax +49 711 22881
On 23/07/15 16:32,
From: Rainer Wiesenfarth
Is the qt.io site - at least the support pages etc. - down or do I have
a
problem at my side of the tube?
As usual: As soon as you click the Send button for the e-mail, the
problem
vanishes...
Best Regards / Mit freundlichen Grüßen
Rainer
Thiago Macieira wrote:
But what about the fact that that those intrinsics are still used even when
configure is called with -no-sse4.1 and -no-sse4.2?
That shouldn't happen. QT_COMPILER_SUPPORTS_SSE4_2 should not be defined, so
this wouldn't evaluate to true:
#if
On Thursday 23 July 2015 20:21:08 René J. V. Bertin wrote:
configure should generate exactly one Makefile: the top-level.
I think that's what it does, but calling qmake -config ltcg immediately
after configure doesn't appear to have any effect.
It should have added -config ltcg to the
On Thursday 23 July 2015 20:35:48 René J. V. Bertin wrote:
Thiago Macieira wrote:
So this is a compiler bug.
Sorry, please try GCC.
On OS X?!
If you want the feature, either switch compilers or fix the bug in this
compiler. The only other option is to stop using the feature.
You'll
I'm getting an error in moc-generated file, and I don't know why.
error: incomplete type 'void' is not assignable
case 1: *reinterpret_cast void*(_v) = _t-camera(); break;
~ ^
The header file contains:
#include QObject
#include QCamera
class
Op 23-7-2015 om 08:42 schreef Thiago Macieira:
Q_GADGET has existed since 4.0.
Sure, but it was undocumented API.
Not quite. It was badly documented API. I think it was mentioned in the 4.8
docs in the Q_OBJECT section.
Guido
___
Interest
Sorry, I got bit by copy-paste. It should be:
Q_PROPERTY(QCamera* setCamera READ camera WRITE setCamera)
Sent: Thursday, July 23, 2015 at 10:56 AM
From: Jason H jh...@gmx.com
To: interest interest@qt-project.org
Subject: [Interest] moc code : incomplete type 'void' is not assignable
I'm
On 23 juil. 2015, at 16:56, Jason H jh...@gmx.com wrote:
I'm getting an error in moc-generated file, and I don't know why.
error: incomplete type 'void' is not assignable
case 1: *reinterpret_cast void*(_v) = _t-camera(); break;
~ ^
The
Den 23-07-2015 kl. 07:57 skrev Gunnar Roth:
Am 23.07.2015 um 07:51 schrieb Bo Thorsen b...@vikingsoft.eu
mailto:b...@vikingsoft.eu:
Den 23-07-2015 kl. 00:07 skrev Thiago Macieira:
Disabling C4244 /* conversion from 'type1' to 'type2', possible loss
of data
*/ is more than going to far. It
From: Rainer Wiesenfarth
Is the qt.io site - at least the support pages etc. - down or do I have a
problem at my side of the tube?
As usual: As soon as you click the Send button for the e-mail, the problem
vanishes...
Best Regards / Mit freundlichen Grüßen
Rainer Wiesenfarth
--
Software
On Thursday 23 July 2015 09:21:13 Jérôme Godbout wrote:
I admit the int to unsigned
int is also a problem to become, -1 lead to 2^32 - 1, we can only do that
if you known negative number aren't used and should do a static_cast
or reinterpret_cast according to the situation and handle the
On Thursday 23 July 2015 09:40:14 Samuel Stirtzel wrote:
2015-07-22 22:52 GMT+02:00 Thiago Macieira thiago.macie...@intel.com:
And then there's another trick... we also began using -isystem with GCC
and
Clang, so they don't complain about warnings in Qt itself :-)
Hi,
is there a trick
On Thursday 23 July 2015 16:05:44 Guido Seifert wrote:
Op 23-7-2015 om 08:42 schreef Thiago Macieira:
Q_GADGET has existed since 4.0.
Sure, but it was undocumented API.
Not quite. It was badly documented API. I think it was mentioned in the 4.8
docs in the Q_OBJECT section.
What's
it should be float f = 2.0f; then. I understand the compiler should check
if value is in range and precision of a float before emitting a warning.
This mostly get annoying inside template function that can handle both
float and double, but putting a float inside a double is ok.
On Thu, Jul 23,
C4244 is particulary true since Qt mostly use int for every size matter,
which on 64 bits system generate a lot of warnings when connecting to Qt. I
hope we see a size_t or equivalent some day. I admit the int to unsigned
int is also a problem to become, -1 lead to 2^32 - 1, we can only do that
if
Thiago Macieira wrote:
git clean -x -d -f in your sources.
(you may want to back up your *.user files from Creator and restore)
That *was* a clean build; Qt 5.4.2 using the release tarball, freshly unpacked
etc.
Patching the toplevel Makefile so that the QMAKE variable includes the -config
Thiago Macieira wrote:
So this is a compiler bug.
Sorry, please try GCC.
On OS X?!
R
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Nice! good to known, thanks Thiago
On Thu, Jul 23, 2015 at 1:23 PM, Thiago Macieira thiago.macie...@intel.com
wrote:
On Thursday 23 July 2015 09:21:13 Jérôme Godbout wrote:
I admit the int to unsigned
int is also a problem to become, -1 lead to 2^32 - 1, we can only do that
if you known
On Thursday 23 July 2015 10:31:01 René J. V. Bertin wrote:
And actually, I'm now fooling around with a project that just builds qtbase
(5.4.2), and it seems that I need -r even immediately after calling
configure.
configure should generate exactly one Makefile: the top-level.
That's also
On Thursday 23 July 2015 10:02:03 manju goudar wrote:
Hi all,
My Target is SPARC little-endian and Linux 3.4.
SPARC can run on little-endian mode? Wow, I didn't know that!
I have ported Qt 4.8.6 to sparc linux.as per my knowledge Sparc and Linux
support is not available in qws folder.
Why
On Thursday 23 July 2015 13:36:05 René J. V. Bertin wrote:
Concerning my test Qt5 build with LTO:
How well supported/tested is doing that in out-of-source shadow build?
It's the only build I do.
After using -march=core2 instead of -march=native (and thus avoiding the
use of SSE4
On Thursday 23 July 2015 11:01:58 René J.V. Bertin wrote:
Thiago Macieira wrote:
That's qhash.cpp (the only place where we use _mm_crc32_xxx()).
This sounds like qhash.cpp was compiled with -march=native but *linked*
without. Can you confirm that you see the compiler options passed on
On Thursday 23 July 2015 08:00:20 Sze Howe Koh wrote:
On 23 July 2015 at 01:03, Guido Seifert warg...@gmx.de wrote:
- the QObject's connections? Will all copies emit the same signals, will
all copies have their slots called?
Worked somehow... probably through magic.
This was my
On Thursday 23 July 2015 08:06:29 Bo Thorsen wrote:
I know, but Thiago said he hadn't seen it actually do any warnings. And
I agree with him that I haven't seen it warn about integer types.
More to the point: I *have* seen warnings about integer conversions to smaller
integers despite this
Op 23-7-2015 om 08:42 schreef Thiago Macieira:
Q_GADGET has existed since 4.0.
Sure, but it was undocumented API.
André
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Sorry, I didn’t intend to bother everyone, just forgot to fill the Subject
line. I’m really sorry.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Den 23-07-2015 kl. 07:51 skrev Berkay Elbir:
I'm searching is there a way to reset to default state of QMainWindow at
runtime?
I have a QMainWindow that has some widgets, user can customize their
locations and save them.
But I want to put a button that resets window states and reverts back to
Thiago Macieira wrote:
That won't work if you already have a build. The propagation only works if
there are no subdirectory Makefiles yet.
If you need to regenerate all the Makefiles, add -r (recursive):
qmake -r -config ltcg $srcdir
Actually, I did, because without -r nothing happened.
Hello
I have strange font problem on iOS 9. Messy fonts are displayed in some texts.
Here is an example screenshot:
https://www.dropbox.com/s/vl0vszob9fupn23/file%2020.7.2015%2015.49.24.png?dl=0
This is QML based app and no problem on iOS 8 or earlier. Any ideas how to fix?
I know that iOS 9
Hello
I have strange font problem on iOS 9. Messy fonts are displayed in some texts.
Here is an example screenshot:
https://www.dropbox.com/s/vl0vszob9fupn23/file%2020.7.2015%2015.49.24.png?dl=0
This is QML based app and no problem on iOS 8 or earlier. Any ideas how to fix?
I know that iOS 9
Op 21-7-2015 om 06:41 schreef Juhani Matilainen:
Hello
I have strange font problem on iOS 9. Messy fonts are displayed in
some texts. Here is an example screenshot:
https://www.dropbox.com/s/vl0vszob9fupn23/file%2020.7.2015%2015.49.24.png?dl=0
This is QML based app and no problem on iOS 8 or
Thiago Macieira wrote:
That's qhash.cpp (the only place where we use _mm_crc32_xxx()).
This sounds like qhash.cpp was compiled with -march=native but *linked*
without. Can you confirm that you see the compiler options passed on the
linker command-line (-O2 -march=native, etc.)?
Well, even
Hi all,
My Target is SPARC little-endian and Linux 3.4.
I have ported Qt 4.8.6 to sparc linux.as per my knowledge Sparc and Linux
support is not available in qws folder.
I have copied linux-generic-g++ to linux-sparc-g++ and changed qmake.conf
as per my toolchain functionality as shown below.
Hmmm... Interesting, it seems that random texts are displayed in wrong
characters. If I kill app and restart some text are now ok but still some
others are mess. And the problem is even editable texts in TextEdit field (also
when to type new texts).
Juhani
André Somers
On 22 Jul 2015, at 22:41, Jason H jh...@gmx.commailto:jh...@gmx.com wrote:
This is not working.
So In QML, I start the backface camera, and it grabs viewfinder frames.
I then call my C++ object which has this function:
bool FlashControl::isFlashSupported(){
camera = new
On 23/07/2015 11:26, Juhani Matilainen wrote:
Hmmm... Interesting, it seems that random texts are displayed in wrong
characters. If I kill app and restart some text are now ok but still
some others are mess. And the problem is even editable texts in TextEdit
field (also when to type new
46 matches
Mail list logo
