debugging_complex_programs
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
debugging_complex_programs [2018/12/26 11:21] – [Debug messages] emozolyak | debugging_complex_programs [2018/12/26 11:27] – [Debug messages] emozolyak | ||
---|---|---|---|
Line 52: | Line 52: | ||
In the script editor, there is a debugging console, which always prints out the functions INFO, DEBUG, ERROR, TRACE regardless of the system log level settings. If the output changes too quickly to analize, you can slow down the script by changging in execution type to " | In the script editor, there is a debugging console, which always prints out the functions INFO, DEBUG, ERROR, TRACE regardless of the system log level settings. If the output changes too quickly to analize, you can slow down the script by changging in execution type to " | ||
- | There are also messaging | + | There are also messaging |
+ | |||
+ | ===== Modular principle ===== | ||
+ | |||
+ | It is recommended that you split complex scripts into simpler and more frequently used functions that you can reuse. Dividing tme into simpler parts, arranging them in the right order and grouping helps to control the logic of the system and makes it easier to set up the system. | ||
+ | |||
+ | |||
+ | |||
debugging_complex_programs.txt · Last modified: 2022/01/15 20:50 by 127.0.0.1