View Single Post
  #2  
Old 08-24-2006, 11:36 AM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 6,015
I would recommend using a different method to implement a run-once step. One way would be to add a build rule something like

%HAS_RUN% is undefined

to the first step, and in the step's vbld_StepDone event, create the global macro HAS_RUN:

Application.Macros(vbldMacroGlobal).Add "HAS_RUN", ""

(see attached sample). This avoids modifying the .bld file and the behavior is more obvious.


As far as refreshing the GUI, use this VBScript code in a Run Script step:

CreateObject("WScript.Shell").SendKeys "{F5}", True
Attached Files
File Type: bld run_once.bld (553 Bytes, 1197 views)
Reply With Quote