OleDropSource Support

[schinagl]

This is work in progress of OleDrop Source. Very work in progress ;-)
I guess the point of this branch currently is that the C implementation of the OleDropSource is there. At least I think that it should work.
I guess it is not working, because we put too little formats on the ole-drop source currently.

Have to investigate on how to do this, since this is rather undocumented. At least I believe

[God-damnit-all]

This repo is advertised in the top issue of Microsoft's archived repo, but two things are concerning:

1. This repo doesn't have Issues enabled.
2. This repo seems to now be significantly behind the archived repo.

[electroly]

Hi @God-damnit-all. Advertising forks seems to be the thing to do with winfile, so I'll link my own fork: https://github.com/brianluft/heirloom. Mine is built atop the final archived upstream commit, issues are enabled and invited, and I am actively working on it because it's my personal daily driver. I implemented this ticket (OLE drag-and-drop source) and more.

[schinagl]

This repo is advertised in the top issue of Microsoft's archived repo, but two things are concerning:

1. This repo doesn't have Issues enabled.

2. This repo seems to now be significantly behind the archived repo.

This repo is not far behind the archived repo. It contains all from the original repo and UNC support.

The dude at the original repo was never brave enough to accept UNC support and that's why I gave up at the original repo.

Later on he crashed the original repo and archived it. What a pity

[schinagl]

Hi @God-damnit-all. Advertising forks seems to be the thing to do with winfile, so I'll link my own fork: https://github.com/brianluft/heirloom. Mine is built atop the final archived upstream.

Great! So there is an active community which let Winfile life on!

I also use my fork as daily tool.