[Interest] QLockFile

[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 you 
think it points to. That may be why that one succeeds.

I have used QLockFile successfully (with "dynamic" paths). So, there 
really is something wrong with your way of using it, not with QLockFile 
itself.

Did you try opening a file yourself at the location you want from code 
using QFile and opening it write only? What happens if you do that?

André

>
> -----Original Message-----
> From: André Somers [mailto:andre at familiesomers.nl]
> Sent: 23 February 2015 10:07
> To: Graham Labdon
> Subject: Re: [Interest] QLockFile
>
> Graham Labdon schreef op 23-2-2015 om 11:00:
>> Hi
>> The filePath is definitely valid
>>
>> The only way I can get QLockFile to work at the moment is by hard coding an invalid c string as in my example.
>>
>> If I use double backslashes in the hard code version tryLock fails
>>
> Are you sure you can actually write at that location?
>
> André
>