Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MAP-21: Fix interia after two finger zoom #694

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

maerki
Copy link
Contributor

@maerki maerki commented Feb 28, 2025

This fixes the 2d inertia after two finger move completed.

Summary by CodeRabbit

  • New Features
    • Enhanced the map’s multi-touch interaction by adding inertia to camera movements. Users will experience smoother and more natural dragging, with improved responsiveness during two-finger gestures.

Copy link
Contributor

coderabbitai bot commented Feb 28, 2025

Walkthrough

The changes modify the MapCamera2d class to improve how drag velocity is handled during two-finger movements. The logic in the onTwoFingerMove method now initializes or updates the drag timestamp and velocity based on movement deltas and elapsed time. In the corresponding onTwoFingerMoveComplete method, the setupInertia method is invoked when the camera is not frozen, enabling inertia-driven movement. No public API changes were made.

Changes

File Change Summary
shared/.../MapCamera2d.cpp Enhanced drag velocity calculation in onTwoFingerMove using time deltas and movement differences; added conditional inertia setup in onTwoFingerMoveComplete.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant MapCamera2d
    User->>MapCamera2d: Start two-finger motion
    MapCamera2d->>MapCamera2d: Check currentDragTimestamp
    alt First movement
        MapCamera2d-->>MapCamera2d: Initialize timestamp and velocity
    else Subsequent movement
        MapCamera2d-->>MapCamera2d: Calculate delta time & update velocity
    end
    User->>MapCamera2d: End two-finger motion
    MapCamera2d->>MapCamera2d: Call onTwoFingerMoveComplete
    alt Camera not frozen
        MapCamera2d->>MapCamera2d: Invoke setupInertia
    end
Loading

Suggested reviewers

  • maurhofer-ubique
  • zimmermannubique

Poem

I'm a rabbit coding swift and light,
Enhancing drags with a velocity flight.
With two-finger moves, the magic begins,
Inertia now flows as the camera spins.
Hopping in code, my joy's set alight! 🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5f1dd95 and 6c3b13c.

📒 Files selected for processing (1)
  • shared/src/map/camera/MapCamera2d.cpp (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: build
  • GitHub Check: build
🔇 Additional comments (3)
shared/src/map/camera/MapCamera2d.cpp (3)

783-794: Nice addition of drag velocity calculation for two-finger movements.

This implementation properly handles velocity calculations during two-finger gestures by tracking timestamps and calculating a weighted average velocity. It matches the approach used in the single-finger move handler and ensures consistent inertia behavior across different interaction modes.


860-860: Good addition of inertia for north-snap rotation case.

Adding setupInertia() here ensures that momentum continues even when the rotation snap-to-north animation is triggered.


865-867: Good conditional handling of inertia.

This properly ensures that inertia is only set up when the camera isn't frozen, matching the condition checks used elsewhere in the code.

✨ Finishing Touches
  • 📝 Generate Docstrings

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@stmitt stmitt force-pushed the bugfix/MAP-21-inertia-after-zoom branch from 5f1dd95 to 6c3b13c Compare February 28, 2025 15:19
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.

2 participants