Skip to content

Smart Drag mixes milliseconds and microseconds #5

Description

@ThrosturX

mouse_hook.c sets event.timestamp from GetTickCount64() (milliseconds). confirmStartTime therefore uses milliseconds, but debounce_check_deferred_releases() obtains now from debounce_get_timestamp(), which returns microseconds when QPC is available.

The code then subtracts these incompatible timestamps, causing the 150 ms Smart Drag confirmation timeout to expire incorrectly.

Use a single timebase/unit for both timestamps.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions