60.1 Background Processing and Autostart
60.1.1 Architecture ¶
The actual processing is done by a dedicated background process (AXPProcessor) that the main program starts and supervises. This has two practical consequences:
- The user interface stays responsive even during large processing runs.
- The main window does not have to be visible - minimized or moved to the notification area, processing continues normally.
A watchdog supervises the background process and restarts it if necessary. If processing shows no sign of life for an unusually long time, the program reports a malfunction.
60.1.2 When is processing active? ¶
| State |
Processing |
| Main window visible, minimized, or in the notification area |
Runs (at the configured check interval, see chapter 40.6.2) |
| Program closed via Exit |
Stopped - on the next start, new files in the monitored folders are picked up |
| Outside the time window (see chapter 40.6.3) |
Paused until the next window |
Recommendation for continuous operation: In the program options, enable Start program with Windows as well as Move to the notification area on startup/close (see chapter 40.5.3) - processing then runs unobtrusively all the time.
60.1.3 Behavior after pauses ¶
After a restart, computer standby, or the end of a time window, the program automatically processes files that arrived in the monitored folders in the meantime - files are not lost due to pauses. Only the pre-existing contents of a newly added folder are deliberately not processed automatically (see chapter 8.8.4); use catch-up processing for that (see chapter 60.2).