On Thu, Oct 10, 2013 at 2:11 PM, Harry van Haaren <[email protected]>wrote:
> On Thu, Oct 10, 2013 at 6:29 PM, Aurélien Leblond <[email protected]>wrote: > >> - what is the cleanest way to access input port data from the GUI? >> > > In short: the DSP part should write an Atom event to notify the GUI. > > The long: Ardour3 deletes UI instances when the window is closed: that > means the state of the UI is lost. > When re-opening the UI, it must re-request the state from the DSP part. > The longer. There are two identical specifications for external-UI. They each have a different URI. If a plugin uses one of them (the original) then Ardour will NOT delete the UI instance when it is closed. If a plugin uses the other (the version "forked"/"copied" by falktx) then Ardour WILL delete the UI instance when it is closed. Both specifications state that the UI is defunct and no longer usable after being closed: * After this callback is called, UI is defunct. Host must call * LV2UI_Descriptor::cleanup(). If host wants to make the UI visible * again UI must be reinstantiated. Just wanted to be clear about this F***ING ABSURD situation. --p
_______________________________________________ Linux-audio-dev mailing list [email protected] http://lists.linuxaudio.org/listinfo/linux-audio-dev
