Reword parts of the changelog

This commit is contained in:
Robbert van der Helm
2020-10-13 15:38:10 +02:00
parent a1162c2256
commit 0602a6e3d4
+15 -15
View File
@@ -13,25 +13,25 @@ Versioning](https://semver.org/spec/v2.0.0.html).
- The way keyboard input works has been completely rewritten to be more reliable - The way keyboard input works has been completely rewritten to be more reliable
in certain hosts and to provide a more integrated experience. Hovering over in certain hosts and to provide a more integrated experience. Hovering over
the plugin's editor while the window provided by the host is active will now the plugin's editor while the window provided by the host is active will now
immediately grab keyboard focus, and yabridge will now return input focus to immediately grab keyboard focus, and yabridge will return input focus to the
the host's window when moving the mouse outside of the plugin's editor when host's window when moving the mouse outside of the plugin's editor when the
the window is still active. This should fix some instances where keyboard window is still active. This should fix some instances where keyboard input
input was not working in hosts with more complex editor windows like _REAPER_ was not working in hosts with more complex editor windows like _REAPER_ and
and _Ardour_, and it will also allow things like the comment field in REAPER's _Ardour_, and it also allows things like the comment field in REAPER's FX
FX window to still function. window to still function.
A consequence of this change is that pressing Space in Bitwig Studio 3.2 will A consequence of this change is that pressing Space in Bitwig Studio 3.2 will
now play or pause playback as intended, but this may also make it impossible now play or pause playback as intended, but this does mean that it can be
to type text with spaces inside of a plugin editor window. Please let me know impossible to type the space character in text boxes inside of a plugin editor
if this causes any issues and we'll try to come up with a middle ground. window. Please let me know if this causes any issues for you.
- Both unrecognized and invalid options will now be printed on started to make - Both unrecognized and invalid options are now printed on started to make
debugging easier. debugging `yabridge.toml` files easier.
- Added a note to the message saying that libSwell GUI support has been disabled - Added a note to the message stating that libSwell GUI support has been
that his is perfectly normal when using REAPER. The message now also contains disabled to clarify that this is expected behaviour when using REAPER. The
the suggestion to enable the `hack_reaper_update_display` workaround for message now also contains a suggestion to enable the
REAPER when it is not already enabled. `hack_reaper_update_display` option when it is not already enabled.
### Fixed ### Fixed