Menus and Toolbars

The Test Device Files screen has its own set of menus and toolbars. When the screen is (by default) docked in the main XJDeveloper GUI, the menus are merged into the application menus, but if the screen is undocked the screen has its own menus.

The toolbar has both editing and debugging items on it:

Compile-time editing options:

• Add Device File... - this button is used to create a new device file  or to add an existing file to the project.
• Remove Device File - this button will remove the file selected in the navigator from the project.
• Configure Devices - this button will be enabled if the selected file in the navigator is being used by a device and requires configuration. Clicking the button will open the Device Configuration Table to allow you to configure all devices using that file. You can also right-click on a selected item in the navigator and click Configure Devices.
• XJRunner Tests - this toolbar dropdown allows you to create a new XJRunner test or add the selected device to a test that already exists. You can also right-click on a selected item in the navigator and click XJRunner Tests.

N.B. Device files can only be removed from the project if no devices are currently assigned to use the file.

• Save... or Save All... - these toolbar buttons or File menu items save files that have been edited. You can also right-click on a selected item in the navigator and click Save.
• Cut, Copy and Paste - these can be used to copy, cut and paste as an alternative to the context menu options or traditional keyboard shortcuts.
• Undo / Redo - these buttons allow you to undo or redo any action within a test device file - the history of actions is unique per test device file, so changes made would be remembered even as you change between files, and can be undone when you go back to that file.
• - the Toggle Breakpoint button allows a breakpoint to be added or removed at the current line of the cursor in the file.

The Debug menu contains options for controlling the debugger when a breakpoint is hit, and for setting and clearing breakpoints. Most of these options are not enabled until the code is running and being debugged.

Run-time debugging options

When tests are being run, if the running code hits a breakpoint that the user has set, the code will pause and the Test Device Files screen will be shown. At this point the toolbar and menus have debugging features enabled (and most of the editing features will be disabled).

The options for controlling the debugger when a breakpoint is hit can also found on the Debug menu.

• Continue - execution will continue until either another breakpoint is reached, or execution completes.
• Step Into - the current line shown in the XJEase editor will be executed, and the debugger will pause on the next line. If the current line is a function call, then execution will stop at the first line inside this function.
• Step Over - the current line shown in the XJEase editor will be executed, and the debugger will pause on the next line of the current function.
• Step Out - the rest of the current XJEase function will be executed, and the debugger will then pause.
• Stop - execution will be stopped.

Printing

When you are using the Test Device Files screen, click Print... on the File menu to print the XJEase code for a device file or additional code file that is currently being edited.