Each SPS can have a single scripting project assigned to it. To access the scripting project associated with an SPS, select the command Tools | Edit Authentic Scripts. This pops up the Scripting Editor window, in which Forms, Event Handlers, and Macros can be created and edited. After the scripting project has been created or edited, it must be saved in memory (by clicking the Save button in the Scripting Editor toolbar (or Ctrl+S)). The scripts in the saved scripting project, however, will only be saved to the SPS when the SPS is saved. So, make sure to: (i) save the scripting project (to memory), and (ii) subsequently save the SPS (to a file location).
To change the scripting language and/or the target .NET Framework, right-click the project, select Project Settings, and make the appropriate selections.
Forms, Event Handlers, and Macros are all created in the Scripting Editor. However, the way they are called and executed is different for each and has a bearing on how you create your scripting projects.
|A Form is invoked by a call to it either within a function in the Global Declarations script or directly in a Macro.|
|An Event Handler runs when the relevant event occurs in Authentic View. If an Event Handler for a single event is defined in both the Global Scripting Project and the StyleVision-project-specific Scripting Project, then the event handler for the project-specific Scripting Project is executed first and that for the Global Scripting Project immediately afterwards.|
|A Macro is executed from within the StyleVision interface by binding it to an Authentic event and triggering that event. In a Macro, it is possible to access all variables and functions declared in the Global Declarations and to display Forms for user input.|
(C) 2019 Altova GmbH