When I try to move a file from my mobile phone (Nokia N95), DO reports an error during the delete part. But it works with Explorer.
The copy part works, but the deletion fails with "An error occurred during moving 'file.jpg': - and the translation from German: "The system can not find the selected file!".
But why can't it be found for deletion? The copy part has worked?
This has to be a bug in DO because it works with Explorer.
See screen shots.
btw: This error happens since earlier versions of DO - I've never reported it.
btw: I just see in DO error message: "Moving from 'Clipboard/Data Source'" .. that's mysterious. I've selected the phone - which has a complete other path.
The copy has worked - as you can see on the screen shot - but the delete of the file fails.
I don't think the two are related. fuzi1968's error is probably due to the Nokia phones using a custom shell extension to display their contents rather than appearing to the OS as a standard drive.
I think the Nokia thing needs to be reported to GPSoftware as it's something they'll need to reproduce and look at in a debugger to work out what Nokia's code is doing and what it's expecting Opus to do.
[quote="leo"]
I think the Nokia thing needs to be reported to GPSoftware as it's something they'll need to reproduce and look at in a debugger to work out what Nokia's code is doing and what it's expecting Opus to do.[/quote]
I think DO should do the same as the normal Windows Explorer because it works with Explorer.
But the only thing exactly the same as Explorer is Explorer. Everything else has to emulate the APIs it provides and may be faced with things that plug into Explorer and assume they are hosted in Explorer itself, depend on undocumented stuff, or whatever. I mean, there are shell extensions out there which send mouse messages to click on parts of Explorer; stuff like that obviously won't work in anything else. So saying that something works in Explorer doesn't mean much until it's been looked into.
Yes, it should work, but it doesn't for some reason. It might be something Opus is doing wrong or something Nokia are doing wrong. If it's something Nokia are doing wrong then maybe Opus can work around it (as it's unlikely Nokia care anyway). Who knows until it has been investigated. Only GPSoftware or Nokia can investigate it with any ease. Nokia are unlikely to care, GPSoftware may need to borrow some Nokia hardware in order to test things, but I know they've done so in the past and fixed stuff so let's hope they can for this as well.
