07 Reporting a bug

Something did not do what you expected. Three things let it be reproduced here — the log of that run, the macro, and what you saw — sent to support@polter-click.com.

  1. Switch on the log categories first

    Settings → Debug → Enabled categories. The log holds only what was switched on while it happened, so check the list before you reproduce, not after. Macro engine, Conditions, Actions and Key output are on by default and cover most problems. Add Screen capture when an object or a colour is not found, Key input when a trigger or a wait-for-key does not fire, Audio for a sound that is not heard, Arduino for a board that does not connect. In doubt, All.

  2. Reproduce it, then export the log

    Do the thing that goes wrong, once. Then Settings → Debug → Export the log — straight away, and before you restart the app: core.log holds the current run only, and every start truncates it.

  3. Export the macro

    On the macro list, the row's ⋯ menu → Export. The file carries the macro's objects, areas and colours, so the same macro runs here. A sound does not travel with it yet — name the sound and say what it was recorded from.

  4. Say what happened

    What you did, what you expected, what it did instead. The game or program it runs against, and whether that was windowed or full screen. A screenshot or a short recording when the problem is something you saw.

What is in the files

The log is a text file of what the app did in that run — condition results, searches, the keys it sent, the paths it runs from. The macro file is your own steps and the pictures they use. One email per problem, the two files attached, the description in the body.