-
v0.5.3-demo — Setup works on a current Mac, and one laptop no longer knocks a shop offline Pre-Release
Suriya released this
2026-09-30 11:39:55 +00:00 | 7 commits to main since this releaseSetup works on a current Mac, and one laptop no longer knocks a shop offline
Four fixes, all found by installing v0.5.2 on a colleague's Mac. Every one of
them failed in a way that looked like something else.Setup could not finish on a Mac with Python 3.14
It picked the newest Python on the machine — which is the one least likely to
have ready-built libraries. Installing then tried to compile numpy from
source and ended in two screens of C compiler errors.Setup now picks a version it knows works, and if the only Python on the
machine is newer than Behavision supports it says so in one line, before
downloading anything, and names the version to install. "Too new" and "too
old" are different messages, because they need opposite actions.Behavision also now works with numpy 2, which is what lets it install on
current Python versions at all.Signing in on a second computer could stop a shop working
Every computer linked to one shop introduced itself to the message broker
under the same name. Brokers require that name to be unique and enforce it by
disconnecting whoever had it first — so two computers on one shop took turns
kicking each other off, over and over.The damage was not limited to the new computer: the shop's own till was the
other half of that loop, so opening the app on a laptop to look at the
product stopped that shop delivering visits, and from either end it looked
like a bad network connection.Each installation now has its own name. Nothing to do — existing installs pick
one up on their next start."no such file or directory" instead of "run setup"
Pressing Start before setup had run reported a 200-character file path and
nothing about what to do. It now says the engine is not installed yet and
names the setup tool — on the button, on the status panel and at startup, so
all three agree.It also detects the case where macOS is running Behavision from a temporary
read-only copy, which happens whenever the app is opened straight from
Downloads. That one is invisible otherwise, and no amount of re-running setup
fixes it: move Behavision to your Applications folder and open it from
there, then run setup.Also fixed
A test that deliberately provoked an unsafe condition could crash the whole
test run on newer OpenCV. It runs in its own process now. This never affected
recognition — the running product has always kept one detector per camera.Downloads
Behavision-v0.5.3-demo-windows-x64.zip— Windows 10/11, 64-bitBehavision-v0.5.3-demo-macos-arm64.zip— Apple Silicon
Unzip, move the app to Applications, run
behavision-setup, then open
Behavision.INSTALL.txthas the steps. On a computer that will not watch
cameras you can skip setup and just sign in.Downloads