It looks like you're new here. If you want to get involved, click one of these buttons!
diff --git a/code/src/main/orxParam.c b/code/src/main/orxParam.c
index e80511e..74d71d9 100644
--- a/code/src/main/orxParam.c
+++ b/code/src/main/orxParam.c
@@ -82,7 +82,7 @@
_orxDebug_SetFlags(orxDEBUG_KU32_STATIC_FLAG_TERMINAL,
orxDEBUG_KU32_STATIC_FLAG_FILE
|orxDEBUG_KU32_STATIC_FLAG_CONSOLE);
- _orxDebug_Log(orxDEBUG_LEVEL_PARAM, (const orxSTRING)__FUNCTION__, __FILE__, __LINE__, STRING, ##__VA_ARGS__)
+ _orxDebug_Log(orxDEBUG_LEVEL_LOG, (const orxSTRING)__FUNCTION__, __FILE__, __LINE__, STRING, ##__VA_ARGS__);
_orxDebug_SetFlags(u32DebugFlags, orxDEBUG_KU32_STATIC_MASK_USER_ALL);
} while(orxFALSE)
@@ -97,7 +97,7 @@
_orxDebug_SetFlags(orxDEBUG_KU32_STATIC_FLAG_TERMINAL,
orxDEBUG_KU32_STATIC_FLAG_FILE
|orxDEBUG_KU32_STATIC_FLAG_CONSOLE);
- _orxDebug_Log(orxDEBUG_LEVEL_PARAM, (const orxSTRING)__FUNCTION__, __FILE__, __LINE__, STRING, __VA_ARGS__)
+ _orxDebug_Log(orxDEBUG_LEVEL_LOG, (const orxSTRING)__FUNCTION__, __FILE__, __LINE__, STRING, __VA_ARGS__);
_orxDebug_SetFlags(u32DebugFlags, orxDEBUG_KU32_STATIC_MASK_USER_ALL);
} while(orxFALSE)
[09:25:11] [LOG] Options:
[09:25:11] [LOG] -c --config Loads the specified configuration file.
[09:25:11] [LOG] -h --help Display this help. You can use extra parameter to display complete description (-h <param>).
Guess the orxDEBUG_KU32_STATIC_FLAG_FILE is the culprit ...diff --git a/code/src/main/orxParam.c b/code/src/main/orxParam.c
index e80511e..0293bc6 100644
--- a/code/src/main/orxParam.c
+++ b/code/src/main/orxParam.c
@@ -601,10 +601,10 @@ orxSTATUS orxFASTCALL orxParam_Register(const orxPARAM *_pstParam)
{
/* Adds it to table */
orxHashTable_Add(sstParam.pstHashTable, u32LongName, pstParamInfo);
-
- /* Process params */
- eResult = orxParam_Process(pstParamInfo);
}
+
+ /* Process params */
+ eResult = orxParam_Process(pstParamInfo);
}
}
else
Comments
thanks for the report!
I fixed the first one by enabling PARAM debug level when the orxParam module gets initialized and the second one is the same fix as you proposed.
Let me know if that works for you!
First one is fine. I'm just curious, does the help message have to contain timestamps?
Second one - almost there ... ;-)
An assert is triggered in orxParam_Process when the parameter is not specified on the command line. Sorry I did not spot this earlier
Here's what fixed it for me:
Cheers,
Graag
Ok, fixed the extraneous tags when display param help (they appeared with a recent refactor I made) and the assert as per your suggestion.