• State Suggested Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 391 subscribers
  • Views 1350 views
  • Users 0 members are here
Options
Related

2017 to 2019 desktop API migration checklist

Alvaro Mira

Hi there,

We have a few scripts making use of the Studio 2017 desktop API to automate some usual task. We are now in the process of upgrading the desktop clients to Studio 2019 so I was wondering if there are any sort of 2017 to 2019 desktop migration checklists available in the community or anywhere else.

The idea is that if there are known issues, recommended solutions, etc., that sort of information can be used to speed up the migration process.

I have performed a few searches but I cannot find what I am looking for.

Best,

A.
Rate translation
×
Suggest better translation
×
Parents
  • 0

    To my best knowledge, SDL does not count with external automation, i.e. things like scripts automating Studio tasks "from outside of Studio" like for example my STraSAK... SDL's official statements always take in account only the very narrow view of "internal" Studio plugins.

    The issues you may encounter after upgrade depend on the functionality you use. They may be caused by changes in the API which even SDL doesn't realize they made them - we have seen the SDL Community developers making updates to their own plugins only after the plugins being reported as failing after update, stating that it's "due to internal changes in the API they did not know about (or something like that).

    For example, I have observed weird behavior of my STraSAK's TMX export/import feature which stopped reporting the progress when used with Studio 2019 and even the recent updates of Studio 2017, throwing some weird error about "ambiguous number of overrides" or something like that in the progress event handler.
    The very same code runs like a charm in Studio 2015 and in not-so-recent builds of Studio 2017.
    Yet, SDL does not mention any API changes anywhere... :(
Reply
  • 0

    To my best knowledge, SDL does not count with external automation, i.e. things like scripts automating Studio tasks "from outside of Studio" like for example my STraSAK... SDL's official statements always take in account only the very narrow view of "internal" Studio plugins.

    The issues you may encounter after upgrade depend on the functionality you use. They may be caused by changes in the API which even SDL doesn't realize they made them - we have seen the SDL Community developers making updates to their own plugins only after the plugins being reported as failing after update, stating that it's "due to internal changes in the API they did not know about (or something like that).

    For example, I have observed weird behavior of my STraSAK's TMX export/import feature which stopped reporting the progress when used with Studio 2019 and even the recent updates of Studio 2017, throwing some weird error about "ambiguous number of overrides" or something like that in the progress event handler.
    The very same code runs like a charm in Studio 2015 and in not-so-recent builds of Studio 2017.
    Yet, SDL does not mention any API changes anywhere... :(
Children