Remove redundant Update call in PartsCanvasPointerReleased

[stakira]

Cleaner alternative to #2409 (fixes the same click track drift).

PartsCanvasPointerReleased called partEditState.Update() with the release point right before End(). Every edit state already gets Update on press and on every pointer move, so the release point only differs from the last processed point when no move events fired (e.g. a touch tap that slips a few pixels) — exactly the case where applying it moves the part without the user dragging.

Behavior notes:

• For a click without movement the removed call is a pure duplicate of the one made on press.
• For a drag, the final position now comes from the last PointerMoved instead of the release point; any remainder is sub-grid (positions are quantized to ticks).
• No state keeps flags in Update that End reads, undo grouping is unaffected, and the final PartsSelectionEvent still fires from CommitTempSelectParts in End.

[Copilot]

Copilot review overview

🟡 Changes recommended

Preserve the final PartPanningState update to avoid visible panning shortfalls.

Get a fresh assessment by requesting another Copilot review.

Review effort: Lite
Findings: 1

Open (1)

• Preserve final panning update on pointer release · New

What changed in this PR

Removes a redundant release-time update to prevent click/tap part-position drift.

Changes:

• Removes the extra Update call before End.
• Preserves edit finalization through End.

File	Review
OpenUtau/​Views/​MainWindow.axaml.cs	Moderate issue (2 votes): retain a final Update for PartPanningState to prevent incomplete middle-button panning.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.