[Interest] Pre-compile system

2015-02-23 Thread Mathieu Slabbinck
Hi, I have a Qt project that uses an external library (linux). The external lib is built statically from source each time using a shell script. To include the lib in the project, I've created a .pri file that defines libx like follows: libx.name = libx libx.target = $$PWD/libx_buil

Re: [Interest] [Development] Qt 5.4 multi-touchscreen problem.

2015-02-23 Thread Jereme Lamothe
I went through this process as well. The Qt libraries that ship w/ the SDK (at least as of 5.3) are built against XInput 2.0, which is too early for multi-touch support. In order to support touch events, I downloaded the xinput 2.2 libraries / headers from the ubuntu repositories and compiled Qt fr

Re: [Interest] QLockFile

2015-02-23 Thread Graham Labdon
Hi Yes, just figured that out. I need to get the lock then open the real file Thanks for your help -Original Message- From: interest-bounces+graham.labdon=avalonsciences@qt-project.org [mailto:interest-bounces+graham.labdon=avalonsciences@qt-project.org] On Behalf Of And

Re: [Interest] QLockFile

2015-02-23 Thread André Somers
Graham Labdon schreef op 23-2-2015 om 12:06: > Hi > > It seems that I needed to do a removeStaleLockFile when I had previously > stopped my program via the debugger. > > I can now get a lock on the file, however, I cannot now open it for writing. Why would you want to write to a lock file? A lock

Re: [Interest] QLockFile

2015-02-23 Thread Graham Labdon
Hi It seems that I needed to do a removeStaleLockFile when I had previously stopped my program via the debugger. I can now get a lock on the file, however, I cannot now open it for writing. This is the pseudo code for what I need to do Lock file Open file Write text Close file Unlock file Is

Re: [Interest] QLockFile

2015-02-23 Thread André Somers
Graham Labdon schreef op 23-2-2015 om 11:36: > Hi > > QString path = "C:\jobs\Test1\job.xcfg"; > QFile file(path); > > bool res = file.open(QIODevice::WriteOnly); > > here res is true But, the path is once again wrong. Use \\ or /, but not \ in string literal paths. > > BUT > > QString path = "C:

Re: [Interest] QLockFile

2015-02-23 Thread André Somers
Graham Labdon schreef op 23-2-2015 om 11:10: > Yes I am sure > I have tried this with numerous file locations and different ways of > constructing a QLockFile and the ONLY on that works is if I hard code an non > escaped file path. The non-escaped path will point to a different location than what

Re: [Interest] QLockFile

2015-02-23 Thread André Somers
Graham Labdon schreef op 23-2-2015 om 10:48: > Hi > > I am trying to use QLockFile in a function that receives a file path as a > QString. > > When I pass the string directly to the constructor of QLockFile and the call > tryLock it always fails. > > However, if I hard code the string the lock su

[Interest] QLockFile

2015-02-23 Thread Graham Labdon
Hi I am trying to use QLockFile in a function that receives a file path as a QString. When I pass the string directly to the constructor of QLockFile and the call tryLock it always fails. However, if I hard code the string the lock succeeds (although I get compiler warnings about unknown esca

Re: [Interest] xcb: moved mouse to .... spamming console

2015-02-23 Thread Koehne Kai
> -Original Message- > From: interest-bounces+kai.koehne=theqtcompany@qt-project.org > [mailto:interest-bounces+kai.koehne=theqtcompany@qt-project.org] > On Behalf Of Guido Seifert > Sent: Saturday, February 21, 2015 1:15 PM > To: interest@qt-project.org > Subject: Re: [Interest]