Subversion Repositories SmartDukaan

Last modification

• Rev 37440 2026-08-27 13:27:35
• Author: amit

• Log message:

  Oppo: slide the drag in eased sub-moves instead of jumping
  
  Aim is solved and it did not finish the job: r37438 lands the ring 0-1px from the
  hole on 103 of 104 drags and oppo still converts ~15%, with POSITION_MISMATCH on
  the rest. So the widget is refusing drags that end in the right place.
  
  Dingxiang scores trajectory and velocity as well as final position and returns the
  same POSITION_MISMATCH for both, so our verdict cannot separate "wrong place" from
  "wrong-looking movement". The circumstantial case for the latter:
  
  oppo 0.91s hold, 2-3 discrete jumps -> 15%
  realme 1.93s hold, slower and more -> 54-74%
  
  and r37438 made oppo FASTER by removing the per-step screenshots, moving it further
  from realme's profile rather than closer.
  
  glide() traverses each leg as up to 18 small sub-moves on an ease-out curve
  (1-(1-t)^2, quick then settling) with a 45ms pause between, so the pointer
  describes a continuous decelerating path instead of teleporting.
  
  Nothing about the DISTANCE changes -- it is still exactly what the derived ratio
  says, and verified to land on it precisely: a 116px leg becomes
  [16,15,13,13,11,10,9,8,6,6,4,3,1,1] and sums to 116. Negative legs work the same
  way for overshoot correction.
  
  To be explicit, since this is the thing not to get wrong: the ratio remains fully
  derived. It starts at zero and comes only from measured movement, per attempt and
  per step. Splitting a leg into sub-moves gives MORE measured legs, not fewer, so
  the estimate sharpens rather than being replaced by an assumption. No constant is
  introduced -- MAX_GLIDE_STEPS, GLIDE_PX_PER_STEP and GLIDE_PAUSE_MS describe the
  path, not the relationship between mouse px and ring px.
  
  Expected hold ~1.7s against realme's 1.93s. Oppo only.
  
  This is a hypothesis test, not a known fix. POSITION_MISMATCH rate answers it in
  one tick; if it does not move, drag dynamics is eliminated and the remaining
  suspect is Hough picking the wrong circle pair on oppo's imagery, which needs
  visual evidence rather than another code change.