On Tue, Aug 18, 2015 at 4:27 PM, Scott Kostyshak wrote:
> On Tue, Aug 18, 2015 at 4:21 PM, Richard Heck wrote:
>> On 08/18/2015 04:19 PM, Scott Kostyshak wrote:
>>>
>>> On Tue, Aug 18, 2015 at 11:12 AM, Richard Heck wrote:
On 08/17/2015 06:13 PM, Pavel Sanda wrote:
>
> Scott Ko
On Tue, Aug 18, 2015 at 4:21 PM, Richard Heck wrote:
> On 08/18/2015 04:19 PM, Scott Kostyshak wrote:
>>
>> On Tue, Aug 18, 2015 at 11:12 AM, Richard Heck wrote:
>>>
>>> On 08/17/2015 06:13 PM, Pavel Sanda wrote:
Scott Kostyshak wrote:
>
> OK good to know. Let's see if anyone el
On 08/18/2015 04:19 PM, Scott Kostyshak wrote:
On Tue, Aug 18, 2015 at 11:12 AM, Richard Heck wrote:
On 08/17/2015 06:13 PM, Pavel Sanda wrote:
Scott Kostyshak wrote:
OK good to know. Let's see if anyone else has an opinion about putting
refresh() into exists().
Is the only reason the bug de
to use lyx over sshfs regularly and
>> so you can imagine what could happen if cache get's clear out all the time
>> and you have report with many images or simialar.)
>
>
> My understanding is that the refresh() call only affects the one QFileInfo
> on which it's ca
images or simialar.)
My understanding is that the refresh() call only affects the one
QFileInfo on which it's called. But if we put refresh() into exists(),
that may clear out a lot of cache.
Richard
On Mon, Aug 17, 2015 at 6:13 PM, Pavel Sanda wrote:
> Scott Kostyshak wrote:
>> OK good to know. Let's see if anyone else has an opinion about putting
>> refresh() into exists().
>
> Is the only reason the bug described in the begining of the thread?
It's the only specific reason I have come acro
Scott Kostyshak wrote:
> OK good to know. Let's see if anyone else has an opinion about putting
> refresh() into exists().
Is the only reason the bug described in the begining of the thread?
Is adding refresh() into the LFUN you want enough to fix the problem.
(I'm one of the victims who need to
ter (5), the PDF viewer is opened for a file that does not exist.
>> This should not happen because LFUN_BUFFER_VIEW_CACHE is only enabled
>> if the file exists, but exists() returns true. I think the reason for
>> this is explained by the following:
>>
>> -
>> (so
, but exists() returns true. I think the reason for
this is explained by the following:
-
(source: http://doc.qt.io/qt-4.8/qfileinfo.html)
To speed up performance, QFileInfo caches information about the file.
Because files can be changed by other users or programs, or even by
other parts of the sam
n for
this is explained by the following:
-
(source: http://doc.qt.io/qt-4.8/qfileinfo.html)
To speed up performance, QFileInfo caches information about the file.
Because files can be changed by other users or programs, or even by
other parts of the same program, there is a function that refreshes
is largely based on the QFileInfo class,
>>> which is thus not reliable anymore if we just want to compare filenames.
>>>
>> If I remember correctly, the reason to use QFileInfo had been to
>> resolve worries about different links that point to the same physical
>&
Vincent van Ravesteijn wrote:
Jean-Marc Lasgouttes schreef:
Vincent van Ravesteijn wrote:
And a second disadvantage of the QFileInfo class is that it is very
unclear when it accesses the filesystem and how you can avoid that
in cases you don't need to.
It's a bit difficult to see
Jean-Marc Lasgouttes schreef:
Vincent van Ravesteijn wrote:
And a second disadvantage of the QFileInfo class is that it is very
unclear when it accesses the filesystem and how you can avoid that in
cases you don't need to.
It's a bit difficult to see how it can be cleaned up. There
Vincent van Ravesteijn wrote:
And a second disadvantage of the QFileInfo class is that it is very
unclear when it accesses the filesystem and how you can avoid that in
cases you don't need to.
It's a bit difficult to see how it can be cleaned up. There is a code
that depends
rgheck schreef:
Vincent van Ravesteijn wrote:
Anyway, our FileName class is largely based on the QFileInfo class,
which is thus not reliable anymore if we just want to compare filenames.
If I remember correctly, the reason to use QFileInfo had been to
resolve worries about different links
Vincent van Ravesteijn wrote:
Anyway, our FileName class is largely based on the QFileInfo class,
which is thus not reliable anymore if we just want to compare filenames.
If I remember correctly, the reason to use QFileInfo had been to resolve
worries about different links that point to the
Hi all,
I reported last week to Qt that the behaviour of QFileInfo::operator==()
changed between version 4.5 and 4.4.3 wrt to non-existent files:
http://www.qtsoftware.com/developer/task-tracker/index_html?id=248471&method=entry.
They have declared it a wont-fix, because if two files do
17 matches
Mail list logo
