In the name of laziness... it most be fairly common that orxConfig_PushSection is called with a input of the name of a object that often is received specific for this, why not have orxConfig_PushSection accept a object directly?
Not sure if this thread requires an answer or not, but the reason why there isn't such immediate shortcut is that the config module doesn't know anything about objects, and introducing a circular dependency would be pretty bad.
Actually the config module doesn't know about anything that exists in orx, beside the file & memory modules.
If you were to use Scroll, there's a method on ScrollObject which allows you to do that:
void ScrollObject::PushSection(orxBOOL _bUseInstanceName = orxFALSE);
By default it'll push the "source" config name and it can optionally push the instance name instance. Every ScrollObject has a unique instance name.
Comments
Actually the config module doesn't know about anything that exists in orx, beside the file & memory modules.
If you were to use Scroll, there's a method on ScrollObject which allows you to do that:
void ScrollObject::PushSection(orxBOOL _bUseInstanceName = orxFALSE);
By default it'll push the "source" config name and it can optionally push the instance name instance. Every ScrollObject has a unique instance name.