You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As shown in the title, I found that MTP responder did not listen for rename events. (for example: mv hello.c hello.java)
(Only the events of adding/modifying and deleting files are monitored for your uMTP-Responder)
So when renaming a file on the MTP responder side, no event occurred, and no event was reported to MTP Initiator .
If want to support this function( renames the file on the MTP responder side, and the MTP Initiator also can update)
I find it possible to do this:
Add events to listen for renamed files: (modify file: src/inotify.c )
I have just tested the modification.
Please note that there was a mistake in the patch (IN_CREATE used instead of IN_DELETE in the delete case).
This is now fixed and all appears to work fine.
Thanks !
Hello.
As shown in the title, I found that MTP responder did not listen for rename events. (for example: mv hello.c hello.java)
(Only the events of adding/modifying and deleting files are monitored for your uMTP-Responder)
So when renaming a file on the MTP responder side, no event occurred, and no event was reported to MTP Initiator .
If want to support this function( renames the file on the MTP responder side, and the MTP Initiator also can update)
I find it possible to do this:
And I I tested it and it worked.
(The MTP Initiator tested are: win7 and win 10)
But I just passed the preliminary verification, and I don't know if there are any bugs.
Do you argee?
Thanks, I wish you a happy life.
The text was updated successfully, but these errors were encountered: