Make sure you have done at least one of the following.
Set at least one breakpoint in the
entry point you want to test.
Create a procedure that invokes
the entry point you want to test.
Create an event that invokes the
procedure.
Click Test
Screen in the Home>Runtime group on
the CimEdit Ribbon bar.
The CimView runtime screen displays.
Important: Global scripts that are loaded into
CimEdit will not necessarily be loaded into CimView when you click
the button.
In order for a global script to be loaded into CimView when you click the
button one of the following has to be true.The script is named in the global
parameter GSM_GLOBAL_SCRIPT or in the files specified by GSM_GLOBAL_SCRIPTCFG .
CimView is already running and the
script is loaded through command lines /loadscript or /loadscriptcfg .
Invoke the event that will start the script or procedure with the script that you want to test.
When Basic comes to the first breakpoint in the script, it opens the Debug Script window.
Note: You cannot debug a script during a regular
CimView session.
At this point, you can:
Edit the code, change break
points, recompile, restart, step into functions etc. in the Debug
Script window. However, if you change the entry point that was
called from the procedure, you will not be able to restart the
script.
Open the Properties dialog
box of an object and make changes to the script. However, you
cannot execute the script from this editor.
Save the changed script in CimView to send the updated script back to CimEdit immediately.
This does not save the script to the screen file.
Return to CimEdit.
Save the screen in order to save the screen file.
Important: It is
recommended that you close the Debug Script window before exiting
Test Screen mode, or before going back to CimEdit and using the
Test Screen button
again.
2. Work with global scripts through CimEdit. |