Multiple times about efsw HOT 8 CLOSED

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

This looks something like the string doesn't have the null character at the end of the string. Can you try a thing? Go to the WatcherWin32.cpp, and memset to NULL szFile before WideCharToMultiByte.

Also, test everything without Qt first if you can.

Regards,

Martín

from efsw.

Original comment by Yash pal (Bitbucket: codeyash, GitHub: codeyash).

Things are working good on linux platform with same code.

Without Qt its no use and I'm not sure how to test.

I will try your comment.

from efsw.

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

Also, you shouldn't be using QString::fromStdString, efsw is UTF-8 in all platforms.

PD: It must be something with your configuration ( since this is being used in other projects for windows ), but i really don't have any clue, you only changed that line reported in the issue #27?

from efsw.

Original comment by Yash pal (Bitbucket: codeyash, GitHub: codeyash).

Weird chars problem gone.

But signals are emitting twice. I've removed QObject usage.

DIR = "N:/Projects/www/vertis" FILE = "new-.png" has event Delete

Any clue/idea to debug this.

DIR = "N:/Projects/www/vertis" FILE = "new-.png" has event Delete

from efsw.

Original comment by Yash pal (Bitbucket: codeyash, GitHub: codeyash).

Part 2 Solved

PART 1 and PART3 are still open

from efsw.

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

Part 3 is not a bug at all, that's the correct behavior. A file being copied is that: open the file, write a chunk of data, then another, and another until the file is completed.

I must clarify that this is not something that i manage manually, this is what the OS is reporting. And the library will respect that. Also think about it, how can i know that the file copy ended? I would need to know the file descriptors that opened that file in write mode and keep track of them until the file descriptor is closed. This is totally out of the scope of the library.

Part 1 seems to be related with the qt issue that you commented before.
But confirm me that the problem is: you're receiving duplicated events for everything or just some of the events?

from efsw.

Original comment by Yash pal (Bitbucket: codeyash, GitHub: codeyash).

Not sure about part 3 but it is extra work it should be done by app and not library. I agree.

But certainly if library can support this , library will be awesome.

from efsw.

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

I'll close this issue.

For part 3, we already discussed that.

For part 1, if you are sure that this happens without any interference of Qt objects continue the conversation in issue #5.

Regards

from efsw.