DavidBrown0954 · 28 Jan 2026, 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 pointsThere'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 pointsYep, separate the event queue from the test clock, otherwise you're just stopping the story before the interesting bit
18 pointsGive 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 pointsAuthor added that. The old event makes the current heading green, but the line below still says waiting. Same thing on every release now.
13 pointsLovely. Two answers on one screen.
9 pointsDoes 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 pointsGrace, this is why I like checking the view separately. A correct stored row can sit under a very convincing wrong colour.
10 pointsNaomi, 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 pointsKeep the export assertion alongside the heading test. Someone can fix one path and accidentally change the other when they tidy the code later.
16 pointsOld-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 pointsSmall 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 pointsHas that build reached the actual workstation yet, or are you still waiting for its update slot?
7 pointsThis discussion is closed to new replies after six months without activity. Last activity: .