Author Topic: MacBook scrolling with trackpad resets to top constantly.  (Read 886 times)


  • Senior Community Member
  • Posts: 239
  • Hero Points: 28
MacBook scrolling with trackpad resets to top constantly.
« on: November 07, 2019, 02:52:24 pm »
On my MacBook Pro, when scrolling in a source file using the trackpad, every time I scroll down the window resets to the top of the file first and then starts the scrolling. It works fine if I use a mouse.

I've seen SE crash a couple of times while scrolling with the trackpad as well.

SlickEdit Pro 2019 (v24.0.0.8)

Serial number: WMX110555
Licensed number of users: Single user
License file: /Library/Application Support/SlickEdit/24/slickedit.lic

Build Date: October 2, 2019   (State file: October 29, 2019)
Emulation: CUA

OS: macOS
OS Version: 10.14.6
Processor Architecture: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz 64 bit (8 cores)

Memory: 90% Load, 14763MB/16384MB Virtual
Shell Information: /Applications/ -i
Screen Size: 1920 x 1200

Project Type: Cpp
Language: .cpp (C/C++)
Encoding: Automatic

Installation Directory: /Applications/
Configuration Directory: /Users/tk7186238/Library/Application Support/SlickEdit/24.0.0/
Migrated from: /Users/tk7186238/Library/Application Support/SlickEdit/23.0.2/

/Users/tk7186238/Library/Application Support/SlickEdit/24.0.0/hotfixes/ (Revision: 3)


  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 3401
  • Hero Points: 465
Re: MacBook scrolling with trackpad resets to top constantly.
« Reply #1 on: November 07, 2019, 03:47:57 pm »
The crash issue popped up a few years ago, and we never had a good enough reproducible case to get to the bottom of it.  I very simple workaround is to turn off drag/drop of text.

Tools > Options > Editing > General / "Allow drag drop of text" to "OFF".

I was not able to reproduce the jumping issue, but I don't have an MBP (Mac mini with Magic Trackpad).  It could be an accidental page gesture, but I'm just guessing here.  Apple has myriads of trackpad options (under TrackPad and then more under Accessiblity), so reproducing the issue might require just the right hardware and settings.