Events
COM specifies that a client must register itself at a server for callbacks using the connection point mechanism. The automation interface for XMLSpy defines the necessary event interfaces. The way to connect to those events depends on the programming language you use in your client. The following code listing shows how this is done using VBScript.
The method WScript.ConnectObject is used to receive events.
To run this code, paste it into a file with .vbs extension, and either double-click in Windows Explorer, or run it from a command prompt.
' the event handler function |
| Note: | For 32-bit XMLSpy, the registered name, or programmatic identifier (ProgId) of the COM object is XMLSpy.Application. For 64-bit XMLSpy, the name is XMLSpy_x64.Application. Be aware, though, that the calling program will access the CLASSES registry entries in its own registry hive, or group (32-bit or 64-bit). Therefore, if you run scripts using the standard command prompt and Windows Explorer on 64-bit Windows, the 64-bit registry entries will be accessed, which point to the 64-bit XMLSpy. For this reason, if both XMLSpy 32-bit and 64-bit are installed, special handling is required in order to call the 32-bit XMLSpy. For example, assuming that Windows Scripting Host is the calling program, do the following: |
1.Change the current directory to C:\Windows\SysWOW64.
2.At the command line, type wscript.exe followed by the path to the script that you would like to run, for example:
wscript.exe "C:\Users\...\Documents\Altova\StyleVision2024\StyleVisionExamples\API\JScript\start.js"wscript.exe "C:\Users\...\Documents\Altova\XMLSpy2024\Examples\API\JScript\start.js" |