Re: More LV2 questions

On Wed, Aug 12, 2026 at 05:49:24PM +0200, Robin Gareus wrote:
 
> The reason for this is that the parameter may be automated. Active
> automation overrides user manual control, unless the automation mode is
> "Touch" and the plugin sends a touch event for the given control

Automation does not require echoing parameter changes sent
by the UI.

Ardour could just send updates for automated parameters that
are in play or touch mode and then only while the user is not
'touching' the corresponding control.

 
> > > 3. A GUI may want to show an optional second window
> 
> Don't do that. This is frowned upon and causes problems on systems without
> z-axis positioning API for windows.
> 
> The only system with a z-axis window stacking API specifically mentions that
> plugins SHOULD NOT open additional windows in their human interface
> guidelines.

The second window only opens when the user requests it, never
on its own initiative. So it can't be more of a nuisance than
any other window the user chooses to open, e.g. another plugin.
or another window of the host. 

It is raised above all others, and if that obscures anything 
the user wants to see, a second click will close it, or the
user can move it out of the way. If it doesn't hide anything
important there is no problem.

Also the plugin UI will be fully functional without that
second window. It does not contain additional controls,
and will typically be opened only for a few seconds to
check something, e.g. the FR of an EQ. The user doesn't
even have to move the mouse to close it. 

How otherwise should a plugin show optional information ?
Let the user resize its single window ? I don't see how
that could be any better.

Ciao,

-- 
FA