Drag+Drop cover image out of Mp3tag to XYplorer doesn't work

Support
1

When you drag+drop a cover image from mp3tag to an external program, sometimes the image is not handled properly. Dropping onto the desktop works, and dropping onto a Windows Explorer folder works. But when using XYplorer and dropping into that, the image is saved as null bytes. The resulting file is put in the correct folder, and is the correct file size, but contains only null bytes. I don't know if the error is related to XYplorer mishandling a drop, or a bug in mp3tag that isn't saving the file properly after receiving a path from the drop. I suppose it depends on how the drop is handled, either by mp3tag or by Windows itself. Can you confirm either way?

2

Which MP3tag version are you using?
Or the other way: does this still happen with 3.28c?

3

Yes, I am using 3.28c.

4

I've checked the code that performs the drop and everything looks good.

I've also tried with XYplorer and can confirm that an empty file with the correct size is produced. I can also confirm that Mp3tag is asked to render the file data and that it's successfully written (from Mp3tag's point of view).

I'm moving this to Support

5

So it's probably a bug in XYplorer then? I would assume that to be the case if the drop is passed off to the external application, but it sounds like you're saying Mp3tag itself is doing the actual writing of the file? If so, I'm confused about where the error could be occuring. I'll bring the bug report over to the XYplorer forums if that's where it belongs.

6

With "writing", I meant that the data is provided by Mp3tag. It's up to the target application to decide what to do with the data.

It could be an issue with XYplorer, but I'm cautious, because I'm also learning new things every day. I'm confident that Mp3tag is working correctly, because Windows File Explorer and Total Commander are both handling the drop just fine.

If you decide to also file a bug with the XYplorer developer, I'd be interested in the outcome or any additional information.

7

OK, thanks! I'll post over there and see what he says.

8

The bug was indeed in XYplorer and has been fixed!