KDirWatch issue
Albert Astals Cid
aacid at kde.org
Mon May 8 15:51:06 UTC 2017
El dilluns, 8 de maig de 2017, a les 17:32:35 CEST, David Faure va escriure:
> On lundi 8 mai 2017 16:14:47 CEST Albert Astals Cid wrote:
> > > I think the point is that we *want* the notification to happen after
> > > restartDirScan, in the cases where stopDirScan/restartDirScan is used.
> >
> > No, we actually have a test that proves that we get to signal after
> > restartDirScan is enabled again
>
> That's what I'm saying yes. We want the notification to happen, and it
> happens.
Sorry, typo, "to signal" is "no signal", since you don't want to open the test
i'll copy the code here
watch.stopDirScan(m_path);
const QString file2 = createFile(2);
QSignalSpy spyDirty(&watch, SIGNAL(dirty(QString)));
QTest::qWait(200);
QCOMPARE(spyDirty.count(), 0);// suspended -> no signal
watch.restartDirScan(m_path);
QTest::qWait(200);
QCOMPARE(spyDirty.count(), 0); // as documented by restartDirScan: no signal
Cheers,
Albert
More information about the Kde-frameworks-devel
mailing list