Public beta 665 - F5/F6 from MTP inserts incorrect file name

Bugs and issues - current donor version.
Post Reply
Message
Author
dsperber
Posts: 221
Joined: 28.03.2010, 01:35

Public beta 665 - F5/F6 from MTP inserts incorrect file name

#1 Post by dsperber » 02.07.2014, 04:07

This problem was previously reported on donor beta forum. It's not clear whether the problem should be re-reported here (since it is still occurring in newest public beta 665) or on donor beta.

This relates to MTP source device (gotten to through the "0" drive, and then selecting "Computer").

Nevertheless, when using F5/F6 to copy/move from one pane to a second pane where the source pane is for an MTP device (e.g. my Samsung Galaxy S4 "screenshots" folder) and the target pane is a folder on my PC's hard drive, the true source file name (as shown in the source pane) IS NOT POPULATED into the copy/move confirmation dialog. Instead, what looks like a Windows system folder name is inserted.

Image

NOTES:

(1) if the "copies the current folder path as text to clipboard" button (upper-right end of the source pane title bar) is pushed, this same strange "system folder" name is copied to the clipboard... rather than the true path\file name as shown in the source pane itself.

(2) if I manually overtype/replace the displayed strange "system folder" name with my own manually typed true file name as shown in the source pane and then push the OK button... NOTHING GET COPIED AT ALL. Nothing happens.

(3) if I manually use the mouse (instead of F5/F6) to drag/drop from source pane to target pane, now the true source file name ends up in the target folder. However there is no "A" (archive) flag bit set on for that copied/moved file in the target folder as would normally be the case for a new or updated file.


dsperber
Posts: 221
Joined: 28.03.2010, 01:35

Re: Public beta 665 - F5/F6 from MTP inserts incorrect file

#3 Post by dsperber » 04.07.2014, 09:19

I would agree with your assessment. Looks like these are all the same issue, dealing with improper handling of MTP-connected devices.

So my problem report is not new... but it also indicates that the problem has been around for a while, has been reported for at least a few months now, and has still not been corrected in the latest recently released public beta 665.

Can't hurt to keep reporting it as long as it's still a problem. The FCXE support for MTP connections is a fantastic new feature, as previously only Windows Explorer could deal with these in an Explorer view... but obviously the new functionality has some defects that make it currently unusable to a significant degree.

Hopefully Marek will respond to one or all of these several threads acknowledging that the problem does exist, and it is currently on his "to-fix" list for an upcoming new donor beta version. Then we wouldn't need to re-report the problem, which based on its age and multiple reports seems to have somehow escaped his eye watching over this forum.

Post Reply

Who is online

Users browsing this forum: No registered users and 47 guests