@memophysic.bsky.social
The legacy API was officially marked deprecated in 2023.1
The removal in 2024.1 was a follow-up to that deprecation.
The change is listed under WG-69350 in the (arguably huge) 2024.1 release notes page, with this link to the migration guide. Hopefully it answers all your questions!
The removal in 2024.1 was a follow-up to that deprecation.
The change is listed under WG-69350 in the (arguably huge) 2024.1 release notes page, with this link to the migration guide. Hopefully it answers all your questions!
Documentation | Audiokinetic
Audiokinetic - The global leader in interactive audio technology.
www.audiokinetic.com
September 2, 2025 at 9:35 PM
The legacy API was officially marked deprecated in 2023.1
The removal in 2024.1 was a follow-up to that deprecation.
The change is listed under WG-69350 in the (arguably huge) 2024.1 release notes page, with this link to the migration guide. Hopefully it answers all your questions!
The removal in 2024.1 was a follow-up to that deprecation.
The change is listed under WG-69350 in the (arguably huge) 2024.1 release notes page, with this link to the migration guide. Hopefully it answers all your questions!
The removal of the legacy Authoring plug-in API was done because this API did not support concurrent GUI instances of a given plug-in instance. This has been necessary since the introduction of object tabs back in 2022.1, which allows duplicate object tabs, including of plug-in GUIs.
September 2, 2025 at 9:28 PM
The removal of the legacy Authoring plug-in API was done because this API did not support concurrent GUI instances of a given plug-in instance. This has been necessary since the introduction of object tabs back in 2022.1, which allows duplicate object tabs, including of plug-in GUIs.