Kinook Software Forum

Go Back   Kinook Software Forum > Visual Build Professional > [VBP] General Discussion
Register FAQ Community Calendar Today's Posts Search

 
 
Thread Tools Rate Thread Display Modes
Prev Previous Post   Next Post Next
  #2  
Old 08-24-2006, 11:36 AM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 6,027
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, 1203 views)
Reply With Quote
 


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



All times are GMT -5. The time now is 11:19 PM.


Copyright © 1999-2023 Kinook Software, Inc.