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

List:       kde-devel
Subject:    Re: Does KDirWatch emit dirty() signal when the current process
From:       "Nicolas Ternisien" <nicolas.ternisien () gmail ! com>
Date:       2007-08-23 8:26:19
Message-ID: ccba71b50708230126v5f5a5bf6u75c4d9bfac7a3cf2 () mail ! gmail ! com
[Download RAW message or body]

Do you all agree with the fact that KDirWatch should emit dirty()
signal if the current process modify a file it is watched ?

If this is the case, I will create a unit test to test and be sure
this is right.

Regards

2007/8/22, Nicolas Ternisien <nicolas.ternisien@gmail.com>:
> Hi Flavio,
>
> Thank you for your answer.
>
> You could find my source code in the KDE SVN :
>
> svn://anonsvn.kde.org/home/kde/trunk/playground/sysadmin/ksystemlog
>
> To launch the unit test, go to the ksystemlog working copy dir, then
>
> cmake .
> make systemReaderTest
> ./tests/systemReaderTest
>
> The source code is in tests/systemReaderTest.cpp and the KDirWatch
> instance is used in src/lib/reader.cpp.
>
> Thanks by advance.
>
> Regards.
>
> Nicolas Ternisien
>
>
> 2007/8/22, Flavio Castelli <micron@bglug.it>:
> > On Wednesday 22 August 2007 09:33:58 Nicolas Ternisien wrote:
> > > Does KDirWatch emit dirty() signal when the current process modify a file
> > it should
> >
> > > In a Unit Test I start my app, then modify the file it's watching
> > > (using QOutputStream and QFile, with flush() and close(), to be sure
> > > lines are correctly written), and then use the QTest::qWait(100000),
> > > to let my app have time to take care of the modification.
> > can you show me your test code (you can also send me a private mail)
> >
> > Cheers
> >         Flavio
> >
> > --
> > |§ micron<- ICQ #118796665
> > |§ GPG Key:
> > |§  ~ Keyserver: pgp.mit.edu
> > |§  ~ KeyID: 6D632BED
> >
> > ~ "Progress is merely a realisation of utopias" ~
> >
> > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
> >
>
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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