Sometimes the code you write won’t behave the way it is supposed to behave. A variable that doesn’t have the proper value, a loop that doesn’t end or even an incorrect selection – all of these things can hurt your development. In this type of situation, a debugger is your greatest ally.
Put a stop point in the suspect part of the code to automatically call the debugger. Follow execution line by line while continually viewing content expressions (variables, fields, pointers, etc.) simply using mouse-over or by selecting the expressions.
The complete list of objects, variables, fields, sets, selections, processes, etc. is also kept up to date and available to let you know the status of your development when the executed line is executed.
A dedicated area displays the call string that displays method concatenation and executed scripts before reaching the break point.
An arrow-shaped cursor in the margin indicates the current line to be executed.
Move the cursor to execute the selected line(s) as many times as necessary or, inversely, to skip a portion of the code. Take advantage and modify the contents of a variable and verify behavioral changes.
In 4D v11 SQL, you can also debug SQL code contained inside the Start SQL / End SQL command. You can also simultaneously debug your SQL code and your 4D code in the same debugger.
Menu Editor >> |