Skip to content

fix: refresh pointer offsets after layout changes - #62

Merged
jourdain merged 2 commits into
masterfrom
fix/pointer-position-after-docking
Sep 25, 2026
Merged

jourdain merged 2 commits into
masterfrom
fix/pointer-position-after-docking

Conversation

@patrickoleary

@patrickoleary patrickoleary commented Sep 25, 2026 •

Copy link
Copy Markdown
Member

Moving a remote-controlled area without resizing it (for example, docking a panel or scrolling its container) leaves the cached element offset stale. Subsequent pointer events then report coordinates relative to the old position.

Refresh the viewport offset when converting each pointer event. This fixes the shared controller used by both React and Vue without requiring a resize event or sending extra size updates.

Note: The failing distance-widget test appears timing-sensitive: its fixed sleeps can expire before RCA finishes processing the queued mouse events. The test now waits for VTK to process the expected mouse releases, with a five-second timeout, while preserving the distance assertions. All eight interaction tests pass locally, and both Vue and React distance tests also pass with an increased event throttle. CI Passes now.

@jourdain
jourdain merged commit 814ef76 into master Sep 25, 2026
7 checks passed
@jourdain
jourdain deleted the fix/pointer-position-after-docking branch September 25, 2026 17:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants