Saved pocket advances on the place request. Stop before release leaves a spacer held and the count ahead
Our FR5 saved pocket advances before placement is confirmed
JackChan1124 · 2026年1月14日 17:45 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
5 条回复
回复 JackChan1124
The request cannot stand in for a completed transfer; have the designer distinguish intended pocket, held part and confirmed placement, including what survives an interruption between confirmation and saving.
12分Agreed. Moving the save later still leaves a gap if placement happens and the save fails
8分回复 JackChan1124
Yes, so retain enough identified transfer state to reconcile that gap, and leave uncertain physical outcomes for the authorised recovery process rather than guessing from the saved pocket.
10分Offline case added: placement completed, save failed, then two restarts. It must stay unresolved through both
14分回复 JackChan1124
Include the receiving tray identity in that case too, because a pocket number alone can look consistent after somebody has exchanged the tray.
15分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .