You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Pharo 12 build 1427, the macOS trackpad and mouse settings option ‘Use inertia when scrolling’ seems to be ignored, with scrolling always acting as if the option is turned off. As described in the Apple Support article ‘Change Pointer Control settings for accessibility on Mac’, scrolling should come to a gradual stop when the option is turned on:
Set options for your trackpad:
[…] Use inertia when scrolling: Control what happens when you lift your finger from the trackpad. With this option turned on, scrolling comes to a gradual stop. Otherwise, scrolling stops immediately.
Click to set options for your mouse:
[…] Use inertia when scrolling: Control what happens when you lift your finger from the mouse. With this option turned on, scrolling comes to a gradual stop. Otherwise, scrolling stops immediately.
On macOS v13.6.6, using the image of build 1427, scrolling always immediately stops; using the image of build 1426, whether it stops immediately or gradually does depend on the system settings. The difference is presumably due to the changes in pull request #16297.
The text was updated successfully, but these errors were encountered:
Since Pharo 12 build 1427, the macOS trackpad and mouse settings option ‘Use inertia when scrolling’ seems to be ignored, with scrolling always acting as if the option is turned off. As described in the Apple Support article ‘Change Pointer Control settings for accessibility on Mac’, scrolling should come to a gradual stop when the option is turned on:
On macOS v13.6.6, using the image of build 1427, scrolling always immediately stops; using the image of build 1426, whether it stops immediately or gradually does depend on the system settings. The difference is presumably due to the changes in pull request #16297.
The text was updated successfully, but these errors were encountered: