-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shifted events in Mac OS v10.7.5 from Finder #47
Comments
Original comment by Martín Lucas Golini (Bitbucket: SpartanJ, GitHub: SpartanJ). Hi Batte, Thank you for reporting it, |
Original comment by Batte HUCHAI (Bitbucket: bhuchai, ). Hello, Thank you for answering me. For your debug logs, I compiled EFSW in debug mode (with "config=debug" instead of "config=release") but it seems to print the same thing (for the same events sequence as described in my initial post) : [Good] With Terminal :
[Bad] With Finder : (n.b. the 3rd step of my initial post is a "touch TEST.txt" done with Terminal)
Note that I use ./lib/libefsw-static-debug.a linked to a Qt C++ project with your main.cpp example (on watched folder "/Users/buchet_b/Documents/Watched/"). Why a Qt project ? Because I would like to use EFSW for a final project which is made with Qt framework (I've actually no choice but it shouldn't be a problem). Does it normally print others lines ? B. |
Original comment by Martín Lucas Golini (Bitbucket: SpartanJ, GitHub: SpartanJ). Sorry, i made a mistake, compiling as debug isn't enough, it is needed to compile with the define EFSW_VERBOSE, if you are using the premake4 file, generate the Makefiles with: premake4 gmake verbose, and then recompile. |
Original comment by Batte HUCHAI (Bitbucket: bhuchai, ). Sorry by advance if I made a mistake but it still seems to print the same. I did : iMac:efsw_project buc_b$ ./premake4 gmake verbose
iMac:efsw_project buc_b$ cd make/macosx/ && make config=debug
iMac:macosx buc_b$ ls -la ../../lib/
|
Original comment by Batte HUCHAI (Bitbucket: bhuchai, ). Indeed, sorry about this "novice mistake" ^.^ So, for the exactly 4 steps of my initial post, I get :
Do not hesitate if you need more information/help. |
Original comment by Martín Lucas Golini (Bitbucket: SpartanJ, GitHub: SpartanJ). Well, i recovered my OS X Lion VM and made an attempt to fix this problems, it should be working. It's probable that you'll still receive more events than expected but it's not an efsw problem, is a combination of the horrible FSEvents events reports and the aggressive file modification that Finder usually does. |
Original comment by Batte HUCHAI (Bitbucket: bhuchai, ). OK, I'm gonna test as soon as possible. Just a question : your advice which consists to return always FALSE in isGranular() function works well but is there some bad effects if we use it (i.e. loss of functionalities, etc.) ? |
Original comment by Martín Lucas Golini (Bitbucket: SpartanJ, GitHub: SpartanJ). Hi Batte, you don't lost any functionality. The difference relies in the fact that i need to keep a copy of the structure of every folder, and that translates in some memory usage. But the memory usage depends on how big is the directory tree that you're watching. Calculate something like 400 KB every 1000 files, it's it something to take in consideration, but depending on the usage, this could be irrelevant or not. |
Original comment by Batte HUCHAI (Bitbucket: bhuchai, ). Hello, I've just tried your commit and good news : it's working ! Indeed, for the same events sequence as described in my initial post, I get :
|
Original report by Batte HUCHAI (Bitbucket: bhuchai, ).
Hello,
I have some troubles with EFSW on Mac OS v10.7.5. Events seem to be sent with a shift ...
For example :
I have 2 files in my watched folder : BAR.txt and FOO.txt
1. I delete BAR.txt : no event is sent.
2. I rename FOO.txt in FOO2.TXT : the below event will be printed :
3. I create TEST.txt : the below event will be printed :
4. I rename TEST.txt in TEST2.txt : the below event will be printed :
So, the only correct step is the number 3. All others seem to be shifted compared to normal way.
It's important to know that if I do the same 3 steps directly by command lines (Terminal), no from Finder, it's working. Is problem coming from Finder ?
Do you have any idea ?
Thanks by advance,
B.
The text was updated successfully, but these errors were encountered: