简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
DavidBrown0954 · 2026年1月28日 02:32 UTC
Hold the old event in a queue and release it after the next attempt starts, through the same handler the application normally uses
20分There's already a pause button in the test but it pauses everything. I need just the first result held, with the second attempt allowed to start.
5分Yep, separate the event queue from the test clock, otherwise you're just stopping the story before the interesting bit
18分Give each queued item a visible attempt reference. Selecting 'release first' gets confusing once the queue contains retries as well as the two original results
-5分Author added that. The old event makes the current heading green, but the line below still says waiting. Same thing on every release now.
13分Lovely. Two answers on one screen.
9分Does the exported inspection list follow the heading or the waiting row? That list is what quality may receive after the screen has changed again.
17分Grace, this is why I like checking the view separately. A correct stored row can sit under a very convincing wrong colour.
10分Naomi, export follows the row, so the plate is still pending there. Author found the heading wasn't checking the attempt reference at all. Patch is in the offline build.
7分Keep the export assertion alongside the heading test. Someone can fix one path and accidentally change the other when they tidy the code later.
16分Old-first, old-last and repeated-current all pass in the patched build. I also tried opening on an unfinished attempt. Heading and export agree now, with the unfinished one still waiting.
16分Small correction to my opening: the result wasn't attached to the next plate in storage. It was shown above it. We've kept the original wording with the reproduction because that's what the operator sees.
22分Has that build reached the actual workstation yet, or are you still waiting for its update slot?
7分此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .