Reword the socket rework changelog entry

This commit is contained in:
Robbert van der Helm
2020-10-27 11:01:55 +01:00
parent e51c7f7ae3
commit dc72dd97a5
+10 -9
View File
@@ -10,15 +10,16 @@ Versioning](https://semver.org/spec/v2.0.0.html).
### Added ### Added
- The way yabridge communicates between its plugin and the Wine host process has - The way communication works in yabridge has been completely redesigned. This
been completely revamped. This was necessary to allow yabridge to handle was necessary to allow yabridge to handle nested and mutually recursive
nested or mutually recursive function calls. What this boils down to is that function calls, as well as several other edge cases. What this boils down to
yabridge became even faster, more responsive, and can now handle a few edge is that yabridge became even faster, more responsive, and can now handle a few
case scenarios that previously required workarounds. This means that yabridge edge case scenarios that would previously require workarounds. This means that
will now work out of the box with _REAPER_ and _Renoise_ and the yabridge no longer requires the `hack_reaper_update_display` workaround for
`hack_reaper_update_display` workaround for is no longer needed. I have been _REAPER_ and _Renoise_, and the loading issues in Bitwig Studio 3.3 beta 1
testing this extensively to make sure that the change does not introduce any have also been resolved. I have been testing this extensively to make sure
regressions, but please let me know if this does break anything for you. that the change does not introduce any regressions, but please let me know if
this does break anything for you.
TODO: Expand on this TODO: Expand on this