[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    SOLVED: Unexpected behaviors in KIO::FileJob async file access
From:       Vlad Codrea <vladc6 () yahoo ! com>
Date:       2007-12-24 20:42:36
Message-ID: 514418.28990.qm () web54406 ! mail ! yahoo ! com
[Download RAW message or body]

--- Thiago Macieira <thiago@kde.org> wrote:
> 
> Have you tried stepping through kio_file? That would be my first
> attempt 
> to understand what is going on wrong.

I stepped through filejob.cpp and and found out that KioFuse was
calling FileJob::read() before the FileJob::opened() signal was sent.
I  had mistakingly assumed that simply having a FileJob object meant
that the object was already usable. Bad idea :)

So now behavior #3 is eliminated. As for behaviors #1 and #2, I still
don't understand why position() and data() signals are being sent
twice, but that's OK since I can work around them.

Thanks,
Vlad


      ____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]