[Interest] Is there a QML way for doing web requests? Just for data, not for rendering.

Hi, You know those fancy REST api's out there. How does one use them in QML? For websockets the answer is simple: QML WebSocket. But i didn't find a way to just do a web request to some url and get it's data, at least not a way that seems "QMLified". Sure, javascript can be used with it's XMLHtt

Re: [Interest] QWE 5.9.3/Linux: chromium build trips over headers from the installed system openssl, protobuf-cpp

René J.V. Bertin wrote: > On Friday December 22 2017 15:00:00 Michal Klocek wrote: > > Hi, > >>I am sorry to say that but your build environment looks broken. >>Returning -I/opt/local/include for glib-2.0 (if this is true) is bogus > > Ah, thanks, it turns out that was indeed a local patch that

Re: [Interest] QDateTime + QXmlStreamWriter on non-UTF8 compatible systems

From: Interest [mailto:interest-bounces+scott=towel42@qt-project.org] On Behalf Of Thiago Macieira Sent: Friday, December 22, 2017 1:22 PM On sexta-feira, 22 de dezembro de 2017 17:21:24 -02 Scott Bloom wrote: > I was able to track down the issue. > > Typically, I was writing to a QString, f

Re: [Interest] Getting "Segmentation Fault" if QML application started without monitor attached

On sexta-feira, 22 de dezembro de 2017 14:55:20 -02 Nenad Lazovic wrote: > . Where does dependency on monitor being attached comes from (QPA > plugin selected, QT build, ..., base class used to initialize app ) ? > > . any suggestion what to change to remove dependency on monitor ?

Re: [Interest] QDateTime + QXmlStreamWriter on non-UTF8 compatible systems

On sexta-feira, 22 de dezembro de 2017 17:21:24 -02 Scott Bloom wrote: > I was able to track down the issue. > > Typically, I was writing to a QString, for some reason, there is an > undocumented difference in the writer for QString vs QIODevice writing. It's not really undocumented. QString is U

Re: [Interest] QDateTime + QXmlStreamWriter on non-UTF8 compatible systems

-Original Message- From: Thiago Macieira [mailto:thiago.macie...@intel.com] Sent: Friday, December 22, 2017 4:10 AM To: interest@qt-project.org Cc: Scott Bloom Subject: Re: [Interest] QDateTime + QXmlStreamWriter on non-UTF8 compatible systems On quinta-feira, 21 de dezembro de 2017 20:

[Interest] Getting "Segmentation Fault" if QML application started without monitor attached

My application is console application (no gui), that runs QQmlEngine, plays qml file, does offscreen rendering (QOffscreenSurface / QOpenGLFramebufferObject) to capture frames to files (every n'th frame). Implementation is very similar to https://gi

Re: [Interest] font smoothing gamma changes in Qt 5.9?

On Thursday December 21 2017 17:05:45 Allan Sandfeld Jensen wrote: >Note newer versions of freetype (since 2.7) already include the most of the >infinality changes as a runtime option. Yeah, Freetype has been getting better but in practice they didn't include the major changes. I think cost wa

Re: [Interest] font smoothing gamma changes in Qt 5.9?

On Donnerstag, 21. Dezember 2017 12:02:21 CET René J.V. Bertin wrote: > Hi, > > Well, it's confirmed: I was seeing the same "watery" rendering on certain > fonts under Linux/X11 using Freetype+Infinality (still on 2.6.5 on Linux; > Mac has 2.7.1 with the same patches). I need a font smoothing gamm

Re: [Interest] Windows 10 + native QFileDialog + QPrinter + some magic = application hangs

Seems the issue is solved: The whole stuff is related to some COM library we (have to) use. During my tests I came along this code snippet in my main.cpp: CoInitializeEx( NULL, COINIT_APARTMENTTHREADED ); // (a) InitialUseOfCOMObject(); // (b) CoUninitialize(); // (c) Using the call s

Re: [Interest] QWE 5.9.3/Linux: chromium build trips over headers from the installed system openssl, protobuf-cpp

On Friday December 22 2017 15:00:00 Michal Klocek wrote: Hi, >I am sorry to say that but your build environment looks broken. >Returning -I/opt/local/include for glib-2.0 (if this is true) is bogus Ah, thanks, it turns out that was indeed a local patch that I should have caught in the original

Re: [Interest] QWE 5.9.3/Linux: chromium build trips over headers from the installed system openssl, protobuf-cpp

Hi I am sorry to say that but your build environment looks broken. Returning -I/opt/local/include for glib-2.0 (if this is true) is bogus and it will include newer openssl headers, since there are in /opt/local/include/openssl, (according to your build log). It looks like sth is misconfigured for

[Interest] No shader program found for DNA

Hello, Should I care about message "No shader program found for DNA" in Qt3D project? I began to receive such messages in Qt 5.10. Thank you. ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QWE 5.9.3/Linux: chromium build trips over headers from the installed system openssl, protobuf-cpp

Konstantin Tokarev wrote: > /usr/include is an implicit search path, so explicit -I options take priority > over it Sure, but that should still mean that openssl headers will be found in /usr/include/openssl when I hide /opt/local/include/openssl . A lot would break if just adding -I/opt/local/

Re: [Interest] QWE 5.9.3/Linux: chromium build trips over headers from the installed system openssl, protobuf-cpp

22.12.2017, 15:46, "René J. V. Bertin" : > Michal Klocek wrote: > >>  might want to check what actually returns -I/opt/local/include/glib-2.0 >>  -I/opt/local/lib/glib-2.0/include -I/opt/local/include. A good starting >>  point might be glib-2.0.pc file (or simply run pkg-config --cflags >>  glib

Re: [Interest] QWE 5.9.3/Linux: chromium build trips over headers from the installed system openssl, protobuf-cpp

Michal Klocek wrote: > might want to check what actually returns -I/opt/local/include/glib-2.0 > -I/opt/local/lib/glib-2.0/include -I/opt/local/include. A good starting > point might be glib-2.0.pc file (or simply run pkg-config --cflags > glib-2.0) Yeah, that'd be the culprit, or a culprit. Q

[Interest] Cannot complie Qt 5.10 on ARM device

Hi, I am now trying to build Qt 5.10 on i.MX6 device (cross compiling is not an option at this moment). I've prepared my custom mkspec called linux-imx6-g++ and I put it in qtbase/mkspecs directory. This works perfectly fine with Qt 5.9.1 and Qt 5.9.3 while with Qt 5.10.0 I get: Could not find qma

Re: [Interest] QDateTime + QXmlStreamWriter on non-UTF8 compatible systems

On quinta-feira, 21 de dezembro de 2017 20:49:33 -02 Scott Bloom wrote: > When using the QXmlStreamWriter to write out an XML file, where one of the > sections is a DateTime Field, and the system is non-UTF8 (Japanese in my > customer case) the XML generated via > > writer.writeCharacters( dateTim

Re: [Interest] building Qt 5.9 on Linux - clang or GCC?

On quinta-feira, 21 de dezembro de 2017 22:00:32 -02 tomek wrote: > And it works also for me too, but command executed during 'configure' > script execution lacks -std=c++11 flag: Ah, so that is the problem. It's passing -std=gnu++11 here, for me. Can you attach the entire config.log? Make sure

Re: [Interest] QWE 5.9.3/Linux: chromium build trips over headers from the installed system openssl, protobuf-cpp

Hi QWebEngine build queries pkg-config for include headers paths, so you might want to check what actually returns -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include. A good starting point might be glib-2.0.pc file (or simply run pkg-config --cflags glib-2.0) B

Re: [Interest] QWE 5.9.3/Linux: chromium build trips over headers from the installed system openssl, protobuf-cpp

Building QWE 5.9.3 with Google's protobuf-cpp 2.x installed also fails :-/ ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest