Explicitly check for CF_HDROP

We should of course not expect all global memory to be a HDROP, oops.
Apparently REAKTOR sometimes uses the drag-and-drop system for its own
internal data.
This commit is contained in:
Robbert van der Helm
2021-07-18 19:20:44 +02:00
parent 0d02951886
commit 28ab46e3c1
2 changed files with 50 additions and 33 deletions
+3
View File
@@ -10,6 +10,9 @@ Versioning](https://semver.org/spec/v2.0.0.html).
### Fixed
- Fixed crashes or freezes when a plugin uses the Windows drag-and-drop system
to transfer arbitrary data. This prevents **Reaktor** from freezing when
editing a patch after upgrading to yabridge 3.4.0.
- Fixed the process status detection treating a process as dead when the user
doesn't have permissions to access the child process's memory. This fixes a
seemingly very rare regression from yabridge 3.4.0 where the Wine plugin host