On Sun, May 1, 2016 at 8:06 AM, Paul Davis <paul@email-addr-hidden>
wrote:
>
>
> On Sun, May 1, 2016 at 8:03 AM, Lorenzo Sutton <lorenzofsutton@email-addr-hidden>
> wrote:
>
>>
>> There's also an interesting user-experience corer to it. For example one
>> thing I noticed in Ardour is when you open a LADSPA plugin window Ardour
>> still 'grabs' keyboard shortcuts (e.g. SPACE to play, HOME to rewind); open
>> an LV2 window and I'm most often hitting HOME to rewind just to discover
>> I've set the parameter under focus (usually a shiny knob) to its minimum
>> value :)
>>
>
> You can disable this by clicking on the keyboard icon in the upper right
> corner of the plugin window. That will give the plugin window the
> opportunity to grab+use all keyboard events.
>
Take 2: What I think you're differentiating between are not actually the
same situation. I think (but am not sure) that when you refer to "an LV2
window" you are talking about plugins which provide their own GUI entirely,
rather than the ones that provide a object that the host can embed in its
own window. This design is now deprecated by many who work on and around
LV2. There's really no way for the "external GUI" approach to ever provide
the same keyboard handling as the embedded approach. By comparison, on OS X
with AudioUnits, there is no "external GUI" option: the plugin's only
choice is to provide an embeddable object, thus allowing the host to
control and provide for a consistent keyboard experience.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-user
Received on Sun May 1 16:15:03 2016
This archive was generated by hypermail 2.1.8 : Sun May 01 2016 - 16:15:03 EEST