Please consider editing your post and mark it as obsolete instead. Do you want to delete post?
Smooth scrolling on OS X?
Permanently deleted user
Created
The smooth scrolling setting seems to have no effect on two computers where I've tried it. But the settings ui gives the impression that this is a valid option. (?)
I just ran into the same thing. It turns out that I think what they mean by "smooth scrolling" is different from what I mean by it, and perhaps different from what you mean by it as well.
On my Mac, if I toggle this setting, then scrolling by pressing PageUp / PageDown (fn + up/down arrows on a MacBook) makes it scroll smoothly, vs. jumping to the destination.
But what I want is smooth, pixel-by-pixel scrolling (a la TextEdit, Safari, etc.) when I move two fingers up/down the trackpad.
I just ran into this in Webstorm, the JetBrains web dev environment. Was evaluating it, but it hurts my eyes to try to watch the text while scrolling in comparison to Sublime Text.
I'm back a year later: my Google search turned up my own post. I'm still looking for an answer to this, now with the latest RubyMine Release Candidate. I suspect it's a problem with Java, and this won't be fixed.
I just ran into the same thing. It turns out that I think what they mean by "smooth scrolling" is different from what I mean by it, and perhaps different from what you mean by it as well.
On my Mac, if I toggle this setting, then scrolling by pressing PageUp / PageDown (fn + up/down arrows on a MacBook) makes it scroll smoothly, vs. jumping to the destination.
But what I want is smooth, pixel-by-pixel scrolling (a la TextEdit, Safari, etc.) when I move two fingers up/down the trackpad.
I would love this!
I just ran into this in Webstorm, the JetBrains web dev environment. Was evaluating it, but it hurts my eyes to try to watch the text while scrolling in comparison to Sublime Text.
I'm back a year later: my Google search turned up my own post. I'm still looking for an answer to this, now with the latest RubyMine Release Candidate. I suspect it's a problem with Java, and this won't be fixed.