Hi Will,

meanwhile I learned a bit more about LV2 and managed to debug the
LV2 plugin while running under Qtractor. This allowed me to see
how the threads and the UI-start are actually handled.
Basically everything was operating as I had expected from theory.

This allowed me then to do those (actually quite minimal) adjustments
to make the LV2 plugin also use the new UI launch scheme with the
"root-Anchor" for the UI sent over the GuiDataExchange channel.

While there are a lot of follow-up questions and things to clean-up
left, the state on my Git branch is now reasonably feature complete
for an first attempt towards testing and integration.

So the question is how best to proceed.
Obviously, you could give the branch a quick test already.
An idea might be also that I just clean-up the Git history a bit,
squash some changesets together and present this as a pull-request.

I would then use a further Git branch for follow-up clean up and
possible bugfixes, while you could start with your work on Config...
We are early in a release cycle, so there is ample time to sort out
any serious problems (and if we hit a real roadblock, I would be able,
with the help of "git rebase" to back out my changes while preserving
your work). Does this sound reasonable?

-- Hermann





_______________________________________________
Yoshimi-devel mailing list
Yoshimi-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/yoshimi-devel

Reply via email to