I am currently encountering a problem with Script Versioning or -- perhaps I don't understand the purpose of Script Versioning...
In CS4 I wrote a Visual Basic Script (see below) that exports INX of the current document to disk. Since CS5 no longer supports INX I thought to use Script Versioning to "simulate" CS4, but obviously that doesn't seem to work. As I have several Scripts to be converted to CS5 I am interested in the constraints using Script Versioning concerning the object model.
Thanks for any help.
Dim myInDesign As InDesign.Application
Dim myPub As InDesign.Document
Set myInDesign = CreateObject("InDesign.Application.CS5")
myInDesign.ScriptPreferences.Version = 6
Set myPub = myInDesign.Documents.FirstItem
myPub.Export "InDesign Interchange-Format", "D:\test.inx"
myInDesign.ScriptPreferences.Version = 7
The reason inx doesn't work, is because it's not a supported feature any more. It has nothing to do with the scripting DOM specifically. Versioning only effects how the scripting DOM interacts with the C++ layer. It can't add missing features...
Think of it as a translation dictionary.
Thanks a lot Harbs.
So I think I was on the wrong track.