ContextMove 4.5.1

ContextMove 4.5.1

Fixes the window buttons on macOS. If you are on Windows, nothing here changes
anything for you.

The window would not come back down

Maximizing the window worked. Clicking the button again to return to a normal
window did nothing, and the window stayed full screen for the rest of the
session — the only way back was to quit and reopen.

The restore path was calling into the wrong piece of macOS. It asked the window
to un-minimize, which is a different operation from un-maximizing and does
nothing at all to a maximized window. ContextMove now remembers where the
window was before you maximized it, and puts it back there.

Closing the app meant it would not open again

Closing the window with the × worked the first time. Opening ContextMove again
afterwards did nothing: the cursor would spin and no window would appear.

Closing the window was leaving the process running. macOS does not always stop
an app the instant its last window goes away, and ContextMove was waiting for a
signal that never arrived. The process stayed alive, still holding the marker
that says "an instance is already running" — so the next launch saw that marker,
concluded ContextMove was open already, and quit without a word.

Closing now shuts the app down properly and clears that marker on the way out.

If ContextMove will not start after updating

An older build may have left one of those stuck processes behind. Open Activity
Monitor, look for ContextMove, and quit it. Then open the app as usual. You only
need to do this once.

Intel Macs

The Homebrew cask now states that ContextMove needs an Apple Silicon Mac. The
app has always been built for Apple Silicon only, but the cask did not say so:
installing on an Intel Mac appeared to succeed and produced an app that could
not open. It now says why, before installing anything, instead of leaving you
with a broken icon and no explanation.

Everything else

Capture, storage, search, and sign-in are unchanged from 4.5.0. Your vault
carries across untouched.