Lower the standard-jiggle minimum distance from 10 px to 2 px (fixes #43) - #53
Open
timokox wants to merge 1 commit into
Open
Lower the standard-jiggle minimum distance from 10 px to 2 px (fixes #43)#53timokox wants to merge 1 commit into
timokox wants to merge 1 commit into
Conversation
…aller#43) Issue bhaller#43 (Microsoft Teams / Slack on modern macOS): those clients don't trust the system idle timer alone for Available/Away — they also look at actual mouse-move events. Activity assertions help keep the OS awake but not those apps. Standard-jiggle's quadratic distance curve had a floor of 10 px (slider value 0 mapped to 0² + 10 = 10), which is more cursor wiggle than some users want for a long-running background jiggle. Drop the floor to 2 px. Curve is now x² + 2 — slider 0 → 2 px, slider 20 → 402 px (clamped to 410 in AppDelegate). 2 px is small enough to be barely noticeable but still registers as motion in the apps that care. The matching safety floor in -periodicJiggleStatusCheck is lowered to match. Slider UI doesn't need a change; the value space at the high end is essentially unchanged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #43.
Microsoft Teams and Slack on modern macOS don't trust the system idle timer alone for the Available/Away switch — they also hook on real mouse-move events. Activity assertions (#44 etc.) keep the OS awake but don't fool those apps. The remaining knob for users in that situation is the standard-jiggle distance, and its current floor is 10 px (slider value 0 mapped to 0² + 10 = 10 in
-[PrefsController jiggleDistance]). That is more cursor wiggle than people want for a long-running background jiggle they don't notice.Fix
Drop the floor to 2 px. Curve is now
x² + 2:2 px is small enough to be barely noticeable but still registers as motion in the apps that care. The matching safety floor in
-periodicJiggleStatusCheck:is lowered to match. The slider UI itself is unchanged — the value space at the high end is essentially identical, only the low end becomes finer-grained.Why minimal
Tried to keep this strictly scoped to the floor change so it can land without dragging in anything else. No new pref, no UI change, no migration concern (the slider value persisted in defaults still maps to the new curve cleanly — users who had it at 0 will now get 2 px instead of 10 px, which is what the issue is asking for).
Verification
xcodebuild -configuration Debug build→ BUILD SUCCEEDED, no warnings. Smoke-test alive.