# Interface

After unzipping and installing the downloaded software, this is what you should see when you run processing.exe:

![The number after "sketch\_" will be related to the date you opened the new project file.](/files/-MRh8GlCVm2hXXt0D1pE)

## Parts of the Interface

### Run and Stop

![](/files/-MRh8dLR0ZZEMOGp6k4z)

The "run" button (looks like a play button) runs your code.

The "stop" button stops running your code - helpful when it has errors or starts to crash your computer.

### Debug and Mode

![](/files/-MRh9AtS8j9pc-kyzkL5)

The debug button helps you go through each part of the code, but the good news is, the program will underline errors and tell you what the error is as you write your code.

The default mode is Java - a coding language that Processing is a derivative of and uses. It is an **explicit** language, meaning you will need to tell it what kind of type each variable is.

### **Code Window**

![](/files/-MRh9soo2fO_4f8oh2A9)

I'm not sure that's what it's called, but you can have multiple tabs to organize your code at the top - each a different file. Along the left are numbered lines to help with finding and fixing errors.&#x20;

### The Console

![](/files/-MRhAKahcyhWCywMm8Uj)

The super important area that tells you what errors you have and provides a way for your code to give you an output text message.

#### Examples

Error when missing a semi-colon:

![](/files/-MRhAimUzaDrI06Kijil)

Notice that there is an unused variable:

![](/files/-MRhAtj5CL85EeBdUZqH)

How a message looks when printed to the console:

![](/files/-MRhBFruTKACp3KhGM10)

Example of the Errors tab and its information:

![](/files/-MRhBUt1VVMOgjgSTCN4)

Here, you see that:

* The error is underlined in the code
* There is a red band in the console with what is causing the error
* It says what tab/file the error is in
* It also provides the line number with the error


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://hopemoore.gitbook.io/coding-for-creatives-spring-2021/processing-info/interface.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
