💥 Rename PluginBridge to WineBridge

I had swapped these names around once before but I think going with
PluginBridge for the plugin and WineBridge for the Wine VST host is the
least ambiguous it can get.
This commit is contained in:
Robbert van der Helm
2020-05-07 13:04:00 +02:00
parent 8b3f5286b4
commit 2d0998047c
7 changed files with 36 additions and 36 deletions
+1 -1
View File
@@ -260,7 +260,7 @@ HostBridge::HostBridge(audioMasterCallback host_callback)
try {
while (true) {
// TODO: Think of a nicer way to structure this and the similar
// handler in `PluginBridge::handle_dispatch_midi_events`
// handler in `WineBridge::handle_dispatch_midi_events`
receive_event(
vst_host_callback, std::pair<Logger&, bool>(logger, false),
[&](Event& event) {
+1 -1
View File
@@ -87,7 +87,7 @@ class HostBridge {
* Ask the VST plugin to process audio for us. If the plugin somehow does
* not support `processReplacing()` and only supports the old `process()`
* function, then this will be handled implicitely in
* `PluginBridge::handle_process_replacing()`.
* `WineBridge::handle_process_replacing()`.
*/
void process_replacing(AEffect* plugin,
float** inputs,