Are there any ways to mess up the orxConfig stack?

edited May 2012 in Help request
Are there any operations that should not be performed in between calls to orxConfig_Push and orxConfig_Pop? Such as the creation or deletion of new Orx objects?

Comments

  • edited May 2012
    Mmh, no, not really.

    Deleting a section that was pushed could be problematic, maybe, but that's the only thing I can think of.
    Using orxConfig_SelectSection() could potentially screw up code calling you when it expected to be in a specific section, hence my advice of always using Push/Pop.
Sign In or Register to comment.