Scense tasks are always executed by Scense Executive, the Session Event being the ‘unit of execution’.
When the execution of a Session Event is nested, a new instance of the Scense Executive is created to execute the ‘second’ Session Event.
This offers possibilities like:
- Using Session Event as ‘components’.
- Creating of conditional loops.
In some cases Scense will automatically use Session Event nesting. (Error Mode, Install Mode).
It is possible to create an infinite loop; consequently, while it seems no result is gained, the memory will fill up due to the continuous creation of new (instances of) Scense Executive Objects until shortage of memory will generate a runtime error.