vanja/yabridge
1
0
Fork 0
mirror of https://github.com/robbert-vdh/yabridge.git synced 2026-05-15 21:15:51 +02:00
Code Issues Packages Projects Releases Wiki Activity

Make YaPluginFactory abstract

Browse Source 
And add separate implementations for the native plugin and the Wine
plugin host. This way we can easily allow the native host to do
callbacks without having to manage a load of lambdas.
This commit is contained in:
Robbert van der Helm
2020-12-05 17:59:31 +01:00
parent 1db3c0371f
commit 049eb257c5
10 changed files with 169 additions and 37 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/common/serialization/vst3/README.md
+4 -3
View File
@@ -43,9 +43,10 @@ instantiated and managed by the host. The model works as follows:
can be sent between the native plugin and the Wine plugin host.
6. If `IFoo` has methods that have side effects (such as instantiating a new
object), then the implementations of those functions in `YaFoo` will be pure
virtual and both the native plugin and the Wine plugin host should provide
their own implementation. Since the functions will ever only be called from
one of the two sides, the other side can just throw in their implementation.
virtual. The side that requested the object (so for the plugin factory that
would be on the side of the native plugin) should then provide a `YaFoo{Plugin,Host}Impl`
that implements those functions through yabridge's `Vst3MessageHandler`
callback interface.
## Plugin Factory