How Do I ... : Test and debug my application : Debug my scripts : Find the coding error : Look at the attribute values of objects used by my application
Look at the attribute values of objects used by my application
Find the error if I used Execute, Display, or InspectFind the error if I used Execute, Display, or InspectNo tips for this topicNo example for this topicFind errors in scripts that run okay, but give incorrect resultsFind errors in scripts that run okay, but give incorrect results
Once you find the coding error that caused the Script Debugger to open, you might find it useful to look closely at the object that caused the error.
To do this, select the script that contains the error from the message stack (middle-left pane). The object that received the selected script and any temporary variables of the selected script are shown in the list of variables (upper-middle pane). The value of any selected variable at the time the error occurred is shown in the values (upper-right) pane.
Inspecting a variable
Double-clicking on a variable in the list of variables opens an Inspector window on that variable.
Using the Inspector window, you can look at the internal state of the object that caused the error. An Inspector window generally lists an object's variables in the left pane and, after you select a variable from the list, the variable's value in the right pane.
Values that are nil or empty when they should have a particular value assigned to them are possible causes of the coding error. To fix the error, change your code so correct values get passed to the object.
For detailed information on using debuggers and inspectors, see the following:
Visual Programming User Guide
Smalltalk User Guide
Last modified date: 07/25/2020