#Report a problem

Help -> Report a problem.

Describe the trouble in your own words: what you did, what you expected, what came out instead. The program gathers the files into one folder and fills the form in advance — what is left is to drag the files in and send it.

#What travels with it

The document is not attached by default. An issue in the tracker is open to everyone, for ever: attach the file and anyone will see the model. The tick is yours and the choice is yours. A report without the document is accepted too — a picture and a description are often enough.

#Two buttons

• Gather the files — puts everything into a folder and shows the path. The button beside it copies the path.
• Open the form — opens the page in a browser with the description already filled in. Drag the files into it from the gathered folder: a link cannot carry them.

Either order works, but gathering first is easier — the folder is then already at hand.

#If the program closed by itself

The next start says so and shows where the record is. That record is the "last crash file" from the table above: switch the tick on and it goes with the report. The message is shown once, but the file stays where it is.

#What to write so it is understood the first time

• What you did — step by step: what you opened, what you selected, what you pressed.
• What you expected — one line. "The fillet should have taken."
• What came out — one line too. "Nothing happened, the part stayed as it was."

The Build line from the About window goes on its own; there is no need to copy it by hand.

#If the buttons do nothing

The buttons stay unavailable until "what happened" is filled in. If the form did not open, check that the system has a browser set; the text is not lost either way — it is in report.md in the gathered folder, and can be pasted into the form by hand.