My feature suggestion is...

Cache Data Used in Cancel Scan to use with following Post Scan

When performing a cancel scan, data for each item is gathered. This data could be cached to use for the subsequent post scan (if the post scan were to occur within a specific time frame). This would speed up the cancel/post routine.

This use of cached data could be turned on or off via a user setting in the event that a user wants live data for the post regardless of when the cancel scan happened.

2 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    James shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Zoran Hranj commented  ·   ·  Flag as inappropriate

        This is exactly the idea I wanted to post just now :)
        Can this idea be revived and maybe reconsidered, now that TSM4 is out?

      Feedback and Knowledge Base