How it works
- It goes through stages in order: the app's process is running, it has a real main window, Windows says it is responding, and optionally its CPU use has calmed down.
- Windows smaller than the minimum size, 400 by 300 unless you change it, count as splash screens; a window that fills its monitor always counts.
- "Responsive" waits for three answers in a row, and the CPU check waits for the load spike to drop and stay steady for the time you set.
- While you wait, the run shows the current stage in plain words, such as the app is loading with its CPU use, instead of just "false".
- The process and main window it found go to later steps, so you can focus or move exactly that window.
Routines that use it
Arrange after loading
Open app starts a heavy design tool, Wait until App is ready with a CPU settle, then Move and resize puts it on your second monitor.
Type into an app safely
After launching a client, wait until it's ready and responding before Type text fills in a search box.
Know when a slow tool has started
Wait until App is ready, then Speak text says it is ready so you can get back to the PC.
Good to know
- The CPU check is skipped when the app was already running well before the wait started.
- Anti-cheat bootstrappers, crash reporters and launcher windows are ignored, even when they're large.
Questions
- How do I make a routine wait until a program is fully open?
- Use Wait until with the App is ready condition after Open app. Turn on the CPU settle check for apps that keep loading after their window appears.
- Why not just add a fixed delay?
- A fixed delay is too short on a slow day and wastes time on a fast one. App is ready moves on as soon as the app is actually usable.