Difference between revisions of "diag scope"

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - " | arma3dev |2.01 " to " | arma3 |2.02 ")
m (Text replacement - "|gr2= Performance Logging" to "|gr2= Performance Profiling")
Line 7: Line 7:
 
|gr1= Diagnostic
 
|gr1= Diagnostic
  
|gr2= Performance Logging
+
|gr2= Performance Profiling
  
 
| 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.

Revision as of 13:46, 25 February 2021

Hover & click on the images for description

Description

Description:
Description needed
Groups:
DiagnosticPerformance Profiling

Syntax

Syntax:
Syntax needed
Return Value:
Return value needed

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

See also:
exitWithdiag_fpsdiag_fpsMindiag_frameNodiag_logdiag_tickTimediag_deltaTime

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