5. Main Window and Control-by-Control Walkthrough

Control	Purpose	How a User Should Think About It
Source project	Points at the original VCL project or source root.	This is the source of truth the converter will scan.
Output folder	Points at the output directory for generated FMX artifacts.	Treat this as disposable and regenerable output, not as your only copy of the application.
Files to convert	Chooses PAS only, DFM only, or both.	Use narrower scopes for focused retests, and use both for full conversions.
Include subfolders	Controls whether subdirectories are scanned.	Leave it enabled for complete projects unless you intentionally want to limit the run.
Report and output actions	Opens the generated report, prints it when supported, or opens the output folder.	Use these after every run so report review is part of the normal workflow.
Critical Areas / Data Aware / 3rd Party / WinAPI	Per-run rule toggles for the specialized conversion families.	Leave these enabled for a normal full pass, and only turn one off when intentionally isolating behavior.
Convert Project	Starts the conversion process.	Only press this after source, output, scope, and rule choices are correct.
Conversion Output log	Displays progress and key messages while also supporting report review.	Read it after every run; it is the first indicator of what happened.

The current v7.0 Atlas main window is a tabbed workspace. Dashboard shows the latest run summary and quick actions. Project Scan holds the path and scope controls, Component Map / Property Map / Event Map expose the live mapper reference surface, Conversion Output shows the live log and report status, and Rules controls the four specialized conversion families. The converter still does its real work behind the scenes, but the operator needs to use the front end carefully because path mistakes, stale output folders, and poorly scoped runs can create misleading results.