![]() ![]() ![]() I don't know when that was added, but it was added ![]() Header has a call, SetUpdateProgressCallback that is not present in theĬS6 version of AIUser.h. I don't have the CC2017 SDK locally anymore (we only supportĬS6/CC2018/CC2019) so I can't compare the headers, but CC2019's AUser.h If you're using code Adobe ships in their examples for loading suites, it shouldn't be too hard to modify it to do that. So it would start with kAIArtSuiteVersion and if that fails, it would try kAIArtSuiteVersion - 1, etc. Thinking about it, a cheap & easy way to do this would be to modify the code that acquires suites so that it doesn't fail when it can't get the requested suite, but instead tries with the next version down. You can get the version of the application from the AIRuntimeSuite, but of course, it also has the same constraints, so be careful. I don't think that will affect you though from the sounds of it. It can get complicated if you're trying to leverage functionality in the higher versions, because you need to account for that in the lower ones. If you wrote your plugin for CC2017 then you're not making any calls to APIs that were added in CC2018 or CC2019, so you don't have that problem. So when you're loading that suite (which I assume you use) you'd have to make sure you don't ask for a version that's not available (i.e. That said, it didn't get updated in CC2019, so the version for CC2018 & CC2019 is the same - 20. The AIArtSuite gets updated in most releases. To do it, you'll need to know what suites you're using and and which versions are available in each release.Į.g. Supposedly releases are backwards compatible for a couple of versions, but it's sort of on you to make that happen. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |