Difference between revisions of "Talk:Activate"
m
the link on self activation does concern the onActivate block, and therefore it is not the same behaviour as some recursive process stacking
imported>HawkFest |
imported>HawkFest m (the link on self activation does concern the onActivate block, and therefore it is not the same behaviour as some recursive process stacking) |
||
| Line 72: | Line 72: | ||
* At the bottom of the article, "[[Activate#Nesting|Nesting]]" section, it is written: | * At the bottom of the article, "[[Activate#Nesting|Nesting]]" section, it is written: | ||
::''You can only nest 5-6 activations at a time. At a time is a little hard to define here, since OnActivate blocks run instantly and before the next line of code is processed. This really means that if 4 other scripts are still being processed and an activation is made during the 5th script, that last activation will be ignored (the script skips the line). This applies to any activation, even if they're different objects or different scripts.'' | ::''You can only nest 5-6 activations at a time. At a time is a little hard to define here, since OnActivate blocks run instantly and before the next line of code is processed. This really means that if 4 other scripts are still being processed and an activation is made during the 5th script, that last activation will be ignored (the script skips the line). This applies to any activation, even if they're different objects or different scripts.'' | ||
:Maybe that you problem is due to some limit imposed by the engine over piling (or stacking) onActivate processes : since the [[onActivate]] block executes fully before going on to the next line of code, a stack is taking place here, as would do a recursive method | :Maybe that you problem is due to some limit imposed by the engine over piling (or stacking) onActivate processes : since the [[onActivate]] block executes fully before going on to the next line of code, a stack is taking place here, as would do a recursive method... | ||