Generic watcher on Windows does not always work recursively

[SpartanJ]

Original report by Nils Desle (Bitbucket: nilsdesle, ).

---

After fixing issue 34 locally, I'm now working with the generic watcher on windows, and its behaviour is not as I expect.

Using the test application, in generic mode (Windows 7), here's the scenario:

1. Inside the watched folder, create a new folder "Level1"
2. Observe that this is detected
3. Inside "Level1", create "Level2"
4. Observe that this is detected
5. Inside "Level2", create "Level3"
6. Observe that this is detected
7. Inside "Level3", create "Level4"
8. Observe that this is detected
9. Inside "Level4", create a file "bla.txt"
10. Observe that this is detected
11. Delete all files and folders at once (Shift-del on "Level1" in explorer)
12. Observe that each folder and file gets a DELETE event

so far so good

13. Create the same folder/file structure OUTSIDE of the watched folder
14. Copy the entire folder structure "Level1" over to the watched folder in one go, using windows explorer
15. Observe that only "Level1" gets an added notification, and nothing else is detected

Not what I expected

16. Add file "test.txt" to "Level4"
17. Observe that NO notification is made, so this new file is not seen or reported

Again, not what I expected

18. Add file "test.txt" to "Level1"
19. Observe that this aded file is reported normally
20. Delete the enire folder structure "Level1" in one go
21. Observe that you get a Delete event for "Level1", "Level1\test.txt" AND a delete event for the "Level2" folder and nothing else (note that "Level2" was never reported as being created!)

Any idea why all this is happening? Combined with issue #34 and #35, I'm getting quite worried here...

[SpartanJ]

Original comment by Martín Lucas Golini (Bitbucket: SpartanJ, GitHub: SpartanJ).

---

Fixed issue #36.
This sould resolve the recursive generic watcher issues.