You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With related to #158 , now we can let plugin provide their native View reflected on the host's SurfaceView. We could provide our default generic view based on androidaudioplugin-ui-compose.
So far, current PluginDetails is not really designed to be usable in standalone form. We need a reasonably shrinked form of the plugin view.
Also, when we want to achieve compact mode (like Logic Pro for iPad or even earlier Bitwig Studio internal plugins panel), we could also provide a compact view for each plugin. The number of parameters there will be limited (filtered by "show on compact" kind of property for each parameter).
The text was updated successfully, but these errors were encountered:
Generic plugin view is alive, and now parameters extension has "priority" property.
We should probably have to think about more than just a generic compact view though: current default UI is already compact-ish, and it is rather a matter of (1) what window size should be the default, and (2) whether we should have bigger UI, not smaller (once bigger ones are set in stone, we could treat current view as "compact").
With related to #158 , now we can let plugin provide their native
View
reflected on the host'sSurfaceView
. We could provide our default generic view based on androidaudioplugin-ui-compose.So far, current
PluginDetails
is not really designed to be usable in standalone form. We need a reasonably shrinked form of the plugin view.Also, when we want to achieve compact mode (like Logic Pro for iPad or even earlier Bitwig Studio internal plugins panel), we could also provide a compact view for each plugin. The number of parameters there will be limited (filtered by "show on compact" kind of property for each parameter).
The text was updated successfully, but these errors were encountered: