diag scope: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "_{10,} " to "") |
Lou Montana (talk | contribs) m (Text replacement - " *\| *([Cc]omments|COMMENTS|Game|[Gg]ame [Nn]ame|Game [Vv]ersion|Game Version \(number surrounded by NO SPACES\)|Multiplayer Arguments( \("local" or "global"\))?|Effects|Multiplayer Effects( \("local" or "global"\))?|Multiplayer Exe...) |
||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:diag_scope}} | {{DISPLAYTITLE:diag_scope}} | ||
{{Command | {{Command | ||
| arma3dev | | arma3dev | ||
|2.01 | |2.01 | ||
|gr1= Diagnosis | |gr1= Diagnosis | ||
|gr2= Performance Logging | |gr2= Performance Logging | ||
| Returns script scope depth. When script is directly executed by the engine or a new script is added to the scheduler, the scope depth is 0. The examples of such execution are event handlers, [[spawn]], etc. [[isNil]] [[Code]] will also create a parent scope. Any use of [[call]] and such will stack execution creating child scopes and increasing scope depth. | | Returns script scope depth. When script is directly executed by the engine or a new script is added to the scheduler, the scope depth is 0. The examples of such execution are event handlers, [[spawn]], etc. [[isNil]] [[Code]] will also create a parent scope. Any use of [[call]] and such will stack execution creating child scopes and increasing scope depth. | ||
| '''diag_scope''' | | '''diag_scope''' | ||
|p1 | |p1= | ||
|p2 | |p2= | ||
|p3 | |p3= | ||
| [[Number]] | | [[Number]] | ||
| Line 41: | Line 41: | ||
}; | }; | ||
}; | }; | ||
};</code> | };</code> | ||
| [[exitWith]], [[diag_fps]], [[diag_fpsMin]], [[diag_frameNo]], [[diag_log]], [[diag_tickTime]], [[diag_deltaTime]] | | [[exitWith]], [[diag_fps]], [[diag_fpsMin]], [[diag_frameNo]], [[diag_log]], [[diag_tickTime]], [[diag_deltaTime]] | ||
| |MPBEHAVIOUR= | | |MPBEHAVIOUR= | ||
Revision as of 01:27, 18 January 2021
Description
- Description:
- Returns script scope depth. When script is directly executed by the engine or a new script is added to the scheduler, the scope depth is 0. The examples of such execution are event handlers, spawn, etc. isNil Code will also create a parent scope. Any use of call and such will stack execution creating child scopes and increasing scope depth.
- Groups:
- DiagnosisPerformance Logging
Syntax
- Syntax:
- diag_scope
- Return Value:
- Number
Examples
- Example 1:
[] spawn { systemChat str diag_scope; // 0 call { call { systemChat str diag_scope; // 2 isNil { systemChat str diag_scope; // 0 call { systemChat str diag_scope; // 1 }; }; }; }; };
Additional Information
Notes
-
Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note
[[Category:Introduced with arma3dev version 2.01]][[ Category: arma3dev: New Scripting Commands | DIAG SCOPE]][[ Category: arma3dev: Scripting Commands | DIAG SCOPE]]
Notes
Bottom Section