Re: [Interest] Slow pointer follow in Qt 5.2.2 (git) on freescale i.MX6 with tslib

Hi Stefano, On Thu, Mar 6, 2014 at 8:47 AM, Stefano Cordibella < stefano.cordibe...@edalab.it> wrote: > Hi list, > using qt 5.2.2 (release branch from git, but I noticed the same issue > with 5.2.1) on I.MX6 it is impossible to flick on qml elements, because the > pointer does not "follow" t

Re: [Interest] Process started with QProcess::startDetached is still a child, and is killed when parent quits

Am Wed, 5 Mar 2014 21:40:11 +0100 (CET) schrieb Wiebe Cazemier : > So, how do I really start a detached process? Is there a similar way to how > Linux parents orphaned processes to init? i have a process to restart a service at a given time, and i do it this way: QProcess* batchProcess=new QP

[Interest] Slow pointer follow in Qt 5.2.2 (git) on freescale i.MX6 with tslib

Hi list, using qt 5.2.2 (release branch from git, but I noticed the same issue with 5.2.1) on I.MX6 it is impossible to flick on qml elements, because the pointer does not "follow" the finger on touchscreen... The strange issue is that with non-qml application (fingerpaint example) or usi

[Interest] Process started with QProcess::startDetached is still a child, and is killed when parent quits

I'm trying to get my auto-updater to work for my Qt 5.1 project (running on Windows 7 32 bit, but Windows XP has the same problem). It downloads an installer, starts it, and quits itself. The problem is that when the application quits, the installer is killed along with it, regardless of the fa

Re: [Interest] Finished resizing a window?

On 24-Feb-2014, at 3:45 PM, Tony Rietwyk wrote: > Good luck - please let the group know what you decide with this. I finally went with a timer: void grafRec::doResizeEvent(QResizeEvent * event) { lastResizeRect.left = lastResizeRect.top = 0; lastResizeRect.right = event->size()

Re: [Interest] llvm thread sanitizer and qmutex

Em qua 05 mar 2014, às 16:01:13, Konrad Rosenbaum escreveu: > Valgrind is confused by this as well... Valgrind usually comes with intercepts for QMutex. It did for Qt 4, at least. I don't know whether it's been updated for Qt 5 yet. Just be glad we didn't leave the locking function inline. Then

Re: [Interest] llvm thread sanitizer and qmutex

Hi, On Wednesday, Wednesday 05 March 2014 at 14:50, Firl, Benjamin wrote: > we make heavy use of Qt in our software and are now trying to use llvm > thread sanitizer for debugging. Unfortunately the sanitizer doesn't seem > to recognize QMutex as a locking mechanism. That's because on Linux it do

Re: [Interest] Weird error using Visual C++ 2013

Le 05/03/2014 13:24, Krzysztof Kawa a écrit : > 2014-03-05 8:59 GMT+01:00 Yves Bailly >: > For what I can see, it seems there's some troubles between QString and > Visual 2013 > initializer-lists implementattion. > > Keeping searching... > > This is a bug

[Interest] llvm thread sanitizer and qmutex

Hallo, we make heavy use of Qt in our software and are now trying to use llvm thread sanitizer for debugging. Unfortunately the sanitizer doesn't seem to recognize QMutex as a locking mechanism. The example below warns about a race condition because the member "data" is accessed in two threads.

Re: [Interest] Weird error using Visual C++ 2013

2014-03-05 8:59 GMT+01:00 Yves Bailly : > > > For what I can see, it seems there's some troubles between QString and > Visual 2013 > initializer-lists implementattion. > > Keeping searching... > > This is a bug in VS2013 initializer_list that basically makes initializer_list useless for anything

Re: [Interest] Weird error using Visual C++ 2013

Le 04/03/2014 17:57, Thiago Macieira a écrit : > Em ter 04 mar 2014, às 15:04:13, Yves Bailly escreveu: >> When trying GCC, either on Linux or using MinGW, it works fine. >> >> Any hint about what may happen? is it a compiler bug, or something else? >> Any idea about a workaround? > > Please valgri