Same community member, second precise report, second round of fixes. This one turned out to be a bug affecting everyone who uses a region box — thank you again.

FIXED: Translations lying completely outside a region box are now swept away the moment you place or move the box. Previously nothing could clean them up: with auto-translate on and a box active, leftovers from full-screen translation froze on screen permanently. The old behavior can be restored with a setting if you relied on it. Also new: the settings window now has an explicit "Exit program" button, so the title-bar X is no longer the only, easy-to-misclick way to quit.

NOTE: Placing a box now means "this is the area I care about" — translations fully outside it are cleared at that moment, while anything overlapping the box is kept and updated as before. F11 still clears everything on screen while keeping your box active.

Everything in this update comes from a feature-request post on our community hub. Please keep them coming — concrete requests like this one turn into updates fast.

NEW: Selecting or changing a translation region now translates it once immediately, so you see a result without turning on auto mode first (can be switched off in Settings). A new option lets the app stop auto-translation when you remove your last region box, instead of switching to full screen. The history window now shows a timestamp for every entry. A quick mode-switch button (game UI / comics and novels) can be added to the main bar — enable it once in Settings, Display tab. The main bar's transparency and size are now adjustable. And the Ollama engine's preset list now goes up to 32B models; any model you have pulled can also be typed in directly.

NOTE: Only the "translate once on region select" behavior is on by default — everything else is opt-in, and the app looks and behaves exactly as before until you touch the new settings. One request we deliberately did not do: merging the game-UI and comics modes. They use fundamentally different text grouping, and guessing wrong would silently produce bad translations — that is what the quick-switch button is for instead.