Re: Fw: Re: More LV2 questions

On Wed, Aug 12, 2026 at 09:12:53PM +0200, Robin Gareus wrote:
 
> The correct flow is: The Plugin UI asks host to change a parameter. The host
> then either allows this or not. If the change succeeded, host informs the
> plugin UI about the new value.
 
Which the UI already knows if it requested the change.

This has the logic upside down.

The only good reason to send a portevent with the correct
value is when value requested by the UI can't be accepted,
e.g. when the parameter is is automation play mode. But then
portevents are sent anyway.


> > > As for telling the Plugin host that the user is touching the control you
> > > need to implement https://lv2plug.in/ns/extensions/ui#touch
> > 
> > Done that a year ago.
> 
> 
> good. Is the code available? Would be nice to have something to test.

It works. What would you like to test ?
 
> > As for managing windows, Ardour itself behaves in way I find
> > really annoying. When you close a plugin window it is not just
> > hidden, it's destroyed. So when the plugin UI is opened again
> > it has to be reconstructed from scratch. Ardour is just decent
> > enough to remember its previous position, but that's all.
> 
> 
> For AU and VST3 there there is a preference for this. The default is to just
> hide the window. LV2 does not have this option.

Are you joking ? With all the extensions, features, options
etc. etc. there's NO way to send a simple command 'please
hide your window' ???

And anyway, normally Ardour provides the parent window.
So hiding this is all it takes.

Ciao,

-- 
FA