AMX NETLINX STUDIO V2.4, Instruction Manual

Page: 109 / 200

Programming
97
NetLinx Studio (v2.4 or higher)
2. File no longer matches:
If you've made any changes to the source file, including a re-save, you'll get a message similar to
the one above. It can often be safely ignored, but select No if you've done any significant editing.
3. Missing files
Breakpoints
Using Breakpoints (NetLinx Only)
While Single Step Mode allows you to execute a single line of code in the Mainline in Axcess
systems, NetLinx systems allow you to use Breakpoints to execute a single instruction in the source
file. You can set a breakpoint on any line of code (other than a comment) that is within the
DEFINE_PROGRAM section.
The following is an example of a SEND_LEVEL breakpoint:
PUSH[dvLocalTP3,1]
PUSH[dvLocalTP3,2]
{
fTestLevel=fTes 1;
SEND_LEVEL dvLocalTP3,1,fTestLevel;
}
Note that semicolons are used in the example to terminate each line in a breakpoint. The only time
that the semicolon is absolutely necessary is when a breakpoint is set at the last line of code. To
keep things simple, consider terminating each breakpoint with a semicolon.
Setting A Breakpoint
1. Place the cursor on a line of code in the DEFINE_PROGRAM section (other than a comment).
2. To insert the breakpoint at the cursor position, right-click to open the Source Code Editor
context menu, and select Toggle Breakpoint, or use the Toggle Breakpoint toolbar button.
3. A red arrow appears in the Source Code Editor window, to the left of the cursor position.
A green bar highlighting the line of code, and the execution arrow (a little green arrow)
indicate the current execution point.
FIG. 17 No Debug Symbols
FIG. 18 File no longer matches