T

duan_jandClaude Fable 5.1 3409d01efd fix(gui): fire mount auto-centering on the first idle status tick

The "apply after mounting" checkbox clicked Auto Centering as soon as the
status poll showed a new sample id. /sample/mount still holds the hw lock
at that point, /alc/center_loop takes the same lock non-blocking, and the
resulting BeamlineBusyException is a quiet error the GUI swallows. So the
automatic click never did anything; only a later manual click worked.

Arm on the sample-id change and click on the first status tick with
busy=False, which is exactly what the user did by hand. Skip arming while
queue automation runs: it mounts and centers on its own and frees the lock
between /scan/auto calls, so a GUI centering in that gap would steal the
lock from the next scan. Pause during a scan's mount phase can still arm
that one sample, but Pause ends in an unmount, so the window is a ms-wide
lock gap sampled at 2 Hz; accepted, noted in the code.

Supersedes the three-commit approach on
fix/auto-center-after-mount-wait-idle (PR 243).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

2026-09-29 16:51:07 +02:00

.gitea

fix: re-pin PySide6 after the beamline-plugin install in CI

2026-09-16 13:28:16 +02:00

.zed

feat: add hostname+user to gui logs

2026-07-06 16:27:08 +02:00

ci: introduce release workflow

2026-07-27 14:44:33 +02:00

docs

docs: udpate cheatsheet formatting

2026-08-04 15:41:29 +02:00