2) Complete IDE Guide

Back to Getting Started

IDE Areas and Their Purpose

• Editor Tabs: each tab is one open file. You can work on multiple files in one session.
• Main Editor: where you write, edit, and navigate code.
• Right Panels (Functions, Types, Labels): symbol navigation for the current file.
• Messages Window: compiler diagnostics, runtime messages, and run status.

The Main File Tab Concept (Important)

When your project has multiple files, one tab is treated as the main file for running/debugging.

• The main file is the startup entry point used when you click Run or Debug.
• Changing the selected tab does not always mean startup file changed.
• If Run seems to launch the wrong file, check which tab is marked as main.

How to Mark a Tab as Main File

1. Open the file you want to use as startup.
2. Right-click that file's tab header.
3. Click Mark as main file in the tab context menu.

After marking, the tab header shows a star (★). That is the visual indicator for the current main file.

How to Unset or Change Main File

• Right-click the same starred tab and choose Unset main file to clear it.
• Or right-click a different tab and choose Mark as main file to switch startup to that file.

Practical Rule

Before running, verify that the tab containing your intended entry code has the star marker.

Run vs Debug (What Is the Difference?)

Both actions compile and launch your program, but they are used for different goals.

• Run (F5): starts the program normally. Use this when you want to play-test behavior quickly.
• Debug (Shift+F5): starts the program with debugger control enabled. Use this when you need breakpoints and step-by-step inspection.

If your program is behaving unexpectedly, Debug is usually the right tool.

Debug Controls and Step Buttons

When debugging and execution is paused at a breakpoint, these controls become important:

• Continue (F5): resume execution until the next breakpoint or program exit.
• Step Into (F11): execute the next statement and enter called routines.
• Step Over (F10): execute the next statement without entering called routines.
• Step Out (Shift+F11): run until the current routine returns to its caller.
• Stop (Shift+Escape): terminate the running/debug session.

Simple Mental Model for Step Buttons

• Into = "show me details inside this call"
• Over = "run this call as one step"
• Out = "finish this routine and go back up"

Suggested Multi-File Workflow

1. Create a startup file (for example, main.lb).
2. Keep startup logic there (window setup, high-level loop, shutdown).
3. Move reusable logic into other files and import as needed.
4. Keep main.lb as the marked main file tab.

Read Errors Efficiently

• Start with the first error shown in Messages.
• Open the reported file and line number.
• Fix only that issue, then run again.

Breakpoints and Debugging Basics

• Set breakpoints on executable lines (not blank lines).
• Run in debug mode, then inspect values while paused.
• Step through logic to see exactly where behavior diverges from expectations.

IDE Habits That Save Time

• Name files by responsibility: main.lb, player.lb, ui.lb, audio.lb.
• Keep functions short and focused.
• Use the Functions panel for quick jumps in large files.
• Run frequently instead of waiting until many changes pile up.

Navigation: Previous: First Launch and First Run | Outline | Next: Programming Fundamentals