![]() |
StepDone fires early on subroutine calls
I have a StepStarting and StepDone handler that I use to time a source control action.
Recently I moved the source control action into a subroutine so I could do several things and call it from multiple places. However this breaks my timing scripts, as the StepDone fires immediately that the subroutine starts This seems counter intuitive to me - the step hasn't finished - it's waiting on all the subroutine steps. I've attached a simple sample. which outputs: Code:
vbld_StepStarting Code:
vbld_StepStarting |
You could use project-level script events:
Code:
Sub vbld_StepStartingProject() |
All times are GMT -5. The time now is 10:47 AM. |
Copyright © 1999-2023 Kinook Software, Inc.