Closed GoogleCodeExporter closed 8 years ago
The problem is because Studio One disposes the editor after the plug-in is
destroyed. (When you quit the app and the plug-in is open.) I was trying to
figure out if this is an actual bug in Studio One or not, but although it seems
backwards it was hard to tell from the AU specs whether this should be allowed
or not.
Philippe's hack works, but it is dangerous as it is actually checking a pointer
in an object that has been destructed. I made a different solution for 1.3b
which should be perfectly safe.
Original comment by malstro...@gmail.com
on 30 Aug 2011 at 10:23
This fixed an issue when removing an instance of my plugin from the 64bit of
Logic.
Original comment by yeaht...@gmail.com
on 2 Sep 2011 at 2:04
Original issue reported on code.google.com by
malstro...@gmail.com
on 13 Jun 2011 at 10:35Attachments: