- Getting a general list of terminal and program properties
- Terminal build number
- Program type and license
- Terminal and program operating modes
- Permissions
- Checking network connections
- Computing resources: memory, disk, and CPU
- Screen specifications
- Terminal and program string properties
- Custom properties: Bar limit and interface language
- Binding a program to runtime properties
- Checking keyboard status
- Checking the MQL program status and reason for termination
- Programmatically closing the terminal and setting a return code
- Handling runtime errors
- User-defined errors
- Debug management
- Predefined variables
- Predefined constants of the MQL5 language
Debug management
The built-in debugger in MetaEditor allows setting breakpoints in the source code, which are the lines on which the program execution should be suspended. Sometimes this system fails, i.e., the pause does not work, and then you can use the DebugBreak function explicitly enforces the stop.
void DebugBreak()
Calling the function pauses the program and activates the editor window in the debug mode, with all the tools for viewing variables and the call stack and for continuing further execution step by step.
Program execution is interrupted only if the program is launched from the editor in the debug mode (by commands Debug -> Start on Real Data or Start in History Data). In all other modes, including regular launch (in the terminal) and profiling, the function has no effect.