![]() |
|
#1
|
|||
|
|||
Pass in another macro value with the log level and use that when calling the child project, specifying the log level.
|
#2
|
|||
|
|||
Thanks. Can you also include a small snippet with VBS on how to set the loglevel in the child when received?
On how to use the following: Code:
Options.LogLevel As LogLevelEnum Please excuse my inability to pickup VBS. Thanks for the help. |
#3
|
|||
|
|||
Code:
Application.Options.LogLevel = %LEVEL_MACRO% |
#4
|
|||
|
|||
Thank you.
|
#5
|
|||
|
|||
I found an interesting observation. Please correct me if i am wrong. In the documentation, it says:
Code:
vbldLogLevelNone 0 No calls to LogMessage will be logged. vbldLogLevelError 1 Only error level messages will be logged. vbldLogLevelWarning 2 Only error and warning level error messages will be logged. vbldLogLevelNormal 3 Errors, warnings, and normal level error messages will be logged. vbldLogLevelDetailed 4 Errors, warnings, normal, and detailed error messages will be logged. vbldLogLevelDiagnostic 5 Errors, warnings, normal, detailed, and diagnostic error messages will be logged. vbldLogLevelNone starts at -1, vbldLogLevelError at 0 and so on. I tested this with: Code:
Builder.LogMessage2 "vbldLogLevelError = " & vbldLogLevelError, vbldLogLevelError |
#6
|
|||
|
|||
You're right, the values in the help are off by one.
|
#7
|
|||
|
|||
Thanks for clarifying.
Is there any variable to get the process' log level during execution? Application.Options.LogLevel only provided the settings set in Application Options > Logging (More) > Log level. I am thinking to get the log level parsed via /loglevel in command line parameter instead of it being parsed as a temp macro. Thanks. |
![]() |
|
|