We need a way to detect that the last script that ran in ACP as a result of a RunScript() call succeeded or failed. A fail includes weather interrupt. Think this one over. The conditions are


    
Script succeeded, ran to completion
    
Script failed with runtime error or compilation error
    
Script was killed by a weather interrupt
    
Script was killed by operator abort

It would allow the logic in Scheduler to be much more robust if we could detect each of these cases.

 

  
SVN Comment
 
 

  
Author
  
rbdenny
 
 

  
Repository
  
svn+ssh://rbdenny@a2_svn_dc3/home/rbdenny/svn/astro/acp
 
 

  
SVN Revision
  
461
 
 

  
Affected files
  
/trunk/ACP Help/ProgRef.chm (Modified)
/trunk/ACP Help/Programmer's Reference/ACP2 Programmer's Reference.mdb (Modified)
/trunk/ACP Help/Programmer's Reference/doc/ProgRef.chm (Modified)
/trunk/ACP Help/Programmer's Reference/doc/ProgRef.hhc (Modified)
/trunk/ACP Help/Programmer's Reference/doc/ProgRef.hhk (Modified)
/trunk/ACP Help/Programmer's Reference/doc/ProgRefUtilPROPScriptCompletionState.htm (Added)
/trunk/ACP Help/relnotes.htm (Modified)
/trunk/ACP Interop Assembly (Scheduler)/Interop.ACP.dll (Modified)
/trunk/ACP-Weather.vbs (Modified)
/trunk/Util.cls (Modified)
/trunk/acp-ref.exe (Modified)
/trunk/doc/ProgRef.chm (Modified)
/trunk/main.frm (Modified)

 
 

  
Check-in comment
  
Add Util.ScriptCompletionState to the API -- for Scheduler.
GEM:848

 

With Scheduler 3.5.3, it's looking at the console text. This is sub-optimal.