Paul Licameli

Results 172 comments of Paul Licameli

Moving `Load` without `LoadCommon` into the wrapper seems wrong. Why were you trying to do it? I think the answer is that you wanted to avoid moving some data members...

You're welcome.

I recall these non-obvious details were discovered in conversation with @vsverchinsky: - `ComponentHandler` objects may be created and destroyed with opening and closing of dialogs (don't need long life), so...

Maybe ComponentHandler can have a longer lifetime if necessary, but it can hold a changing pointer to EffectSettingsAccess which may sometimes be null. But then I think it must be...

My thoughts after talking to @pietro68 today and studying the code; let's us three talk again on Monday. The model I'm trying to use in the new framework is this:...

I understand now that it is this line in `VST3Effect::VST3Effect`: ``` mEditController->setComponentHandler(mComponentHandler); ``` that sets up for Steinberg to call back into whatever methods we implement for the transferring of...

Friends, you all forked too early. Retargeting to another toolkit, when the accumulated code of many years wasn’t as careful as it could have been with separation of UI logic...

> I suppose merging updates from Audacity regularly would be the most realistic path towards this. That has lots of implications, for example, we may decide to hold off on...

> > Friends, you all forked too early. > > Honestly, @Paul-Licameli, don’t take it personally, but you don’t get to call the shots on whatever other people do in...

> Honestly, I don't think we care too much about compatibility with upstream. The only thing I'd care about personally is merging unfinished/half-finished features as seen in #515 and audio...