I am on a trip so replying quickly with my mobile...
I agree that the filename clss has become too complicated because of
all the corner cases. Still, it has served its purpose and fixed a lot
of bugs and portability problems.
Coming back to our problem, i think we need a fileName::isSimilarTo()
me
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 how it can
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 is a code
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 on the Qt version
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 tha
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 sa
