It looks like you're new here. If you want to get involved, click one of these buttons!
Just a few short questions relating to the orxParam module of Orx:
If I wanted to re-purpose the -c parameter for something else, how could I do that? The tutorial here https://orx-project.org/wiki/en/tutorials/system/commandline_parameters only works for everything except the above default parameters.
If I wanted to test for other optional arguments passed, but not create handlers for them? How would I go about this. I assume all params are set using orxParam_SetArgs(argc, argv), but how could I access them? For example, if I wanted to test if the user specified an -x argument but I have no handler set up for it, how is that done? Standard c args tests perhaps?
Last case, if I have a handler for a parameter, and the argument is passed, the handler will execute. That much is good. But how did I test if the user did not pass the argument. Standard c testing code here as well?
It's very likely all my use cases above are intertwined. I can work around them but it would be cleaner if I can understand how to access anything collected by the orxParam module.
If I have a go at answering this myself: the job of orxParam_SetArgs(argc, argv) is to allow arguments to be available for registration to handlers. Any missing parameters, is the probably still the job of the developer to enumerate by checking the argv array?
-hbe universal among all orx-based tools/utilities.
You should never need to check the C args yourself. Going through the unified
orxParamsystem means your application will always support standardized parameters the way orx understands them.
Here's a quick example to illustrate the above, for clarity sake. It'll check for the presence of
That's perfect thank you. I'll extend the wiki article with this detail.