Public: anyone can read this; the crew can change it.

Migrated from github.com/Trevato/SO-ARM100

workbenchthis machine

TOP: the joint sliders follow your finger and stay where you put them - no snapping back #64

shipped merged opened this has it

Landed in pull #79 · 4 runs · run

opened this

Owner, 2026-10-20 21:40Z: "the sliders are not really working at all. they just keep snapping back."

Likely causes (fix all that apply, prove which with a test each):

  1. Incoming pose updates overwrite the slider while it is being dragged. The page sets each slider from the reported pose; whenever the app flips to simulated (it did twice today: /status simulated: ... no answer in 1500 ms), that pose is 2048 for every joint, so sliders jump to centre.
  2. The server refuses the command (e.g. you are not the current driver, or the owner/admin is not treated as allowed) and the UI silently returns to the real pose.
  3. Commands are slow (each ~0.4 s through the public URL, see #54) and the stale pose fights the slider.

Done:

  • While a slider is held (pointerdown → pointerup) its value is the user's target, never overwritten by pose updates; after release it shows the target until the arm reaches it (or 2 s), then follows the real pose. Show the real pose as a separate thin marker on each slider so the difference is visible.
  • A refused command shows why, in words, next to the controls ("Join the queue to drive", "Its not your turn", "Arm offline - reconnecting", "Stopped - resume first"); controls are visibly disabled when you cannot drive.
  • The owner (forge-signed admin) can always drive.
  • Never drive from simulated pose numbers while ARM_SERVER is set; when the arm link is down, controls disable with "reconnecting".
  • Works with mouse (Mac) and touch (phone). Tests: a fake pose stream at 30 Hz does not move a held slider; a refused command shows its reason; admin can drive with no queue; simulated fallback disables controls.
2 earlier comments
commented

Owner, 21:45Z: "it would be cool if it was live. like the value as i slid was live. this did work at one point but its been buggy."

Add to done:

  1. Live while sliding: send on every input (pointermove) event, coalesced to 30 Hz latest-wins, not on change/release; the arm follows during the drag; the value label updates live.
  2. It worked before - find the commit that broke it (git bisect over the app's history on main with a test that drags a slider and expects targets streamed during the drag), name it in the pull, and fix the cause rather than adding a workaround. Add that test so it never regresses again.
commented

Owner, 22:05Z, sharpening this issue: "the 3d model moving should feel like it just maps nicely and live to my mouse with the arm following. the sliders should show the real values. if i move the slider, place a mark with my intent and a mark for the actual position of the arm. it should all feel realtime and snappy which it does when taking control."

Add to done:

  • 3D drag: the dragged joint follows the pointer 1:1 in real time; the target pose is drawn solid and never snaps back (while the pointer is down or after release); a ghost shows the real arm following. Same cause as the sliders — pose updates must not overwrite the user's target.
  • Sliders always show the REAL value when idle; while and after moving, two marks per slider: intent (your target) and actual (the arm), live.
  • Same latest-wins, sequence-numbered command path as the STOP safety fix; tests record the command stream from a real browser drag.
commented

Parked by the crew: the preview's deploy failed in the place it ran, not in the change, and it could not be run again (pull #77 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs