> On 6 Dec 2017, at 19:11, Thiago Macieira wrote:
>
> On Wednesday, 6 December 2017 04:58:32 PST Shantanu Tushar wrote:
>> Most likely the "device not open" message is being output when you
>> call `.exists()` on the file, followed by your qDebug.
>
> Right, it's
On Wednesday, 6 December 2017 04:58:32 PST Shantanu Tushar wrote:
> Most likely the "device not open" message is being output when you
> call `.exists()` on the file, followed by your qDebug.
Right, it's the exists() call that causes it.
I don't think that message comes from Qt. I can't find it
Most likely the "device not open" message is being output when you
call `.exists()` on the file, followed by your qDebug.
On Wed, Dec 6, 2017 at 6:23 PM, Emre Besirik wrote:
>
>> On 5 Dec 2017, at 18:39, Thiago Apperantly wrote:
>>
>> On Tuesday, 5
> On 5 Dec 2017, at 18:39, Thiago Apperantly wrote:
>
> On Tuesday, 5 December 2017 03:26:41 PST Emre Besirik wrote:
>> Hello list,
>> QFile fails on Windows when screen is locked with message "device not open”?
>> And it is on new QFile(“somefile.txt”) not on
On Tuesday, 5 December 2017 03:26:41 PST Emre Besirik wrote:
> Hello list,
> QFile fails on Windows when screen is locked with message "device not open”?
> And it is on new QFile(“somefile.txt”) not on file.open(ReadOnly).
Your analysis cannot be right. The QFile creation does not touch the file
Hello list,
QFile fails on Windows when screen is locked with message "device not open”?
And it is on new QFile(“somefile.txt”) not on file.open(ReadOnly).
I’ve recently stumbled this problem and not sure the real cause of it and
decided to ask you guys.
And I’m sure that this has only started to