The scripting engine used by IMatch 5 is compatible with the scripting engine used by IMatch 3.6.0.118 released more than one year ago. This is for the Basic language dialect etc.
The scripting object model in IMatch 5 has changed for the first time in almost 10 years. This step was required, and it may brake some existing scripts. The Beta test phase (almost 12 months) gave uses the chance to convert their scripts as needed. If you did not participate the in the Beta test, you will have to migrate your scripts now, if the functionality provided by your scripts is not available in IMatch 5 anyway.
I have more than 20 scripts to convert in a short time.
The Beta test for IMatch 5 ran for almost a year. Why did you not participate and converted your scripts without pressure during that year?
Did you read the
Script Migration Guide in the help? This should get you started. You'll find it by typing
Migrate in the help index and then clicking on the
IMatch 3.x scripts entry. The Migration Guide lists the major changes, explains which classes have been replaced etc. For example, I read there
IPTCStream Retired. Use the
Metadata classes instead.
which tells me that IPTCStream is no more and that I have to use the new universal
Metadata classes instead. These classes not only handle all metadata supported by IMatch, including IPTC, EXIF, XMP, GPS, PDF in a universal fashion, but also allow you to write not only IPTC but XMP and EXIF as well.