![]() Why would it be moving slowly? Are you talking about the Lion-and-up "scroll inertia"? I have that disabled, because it's annoying to me. Is the hesitation that you feel that scroll animations in general are fundamentally broken, or that they don't belong in a text editor, or that they don't belong in MacVim? (Imagine if your mobile apps or web pages had the same behavior). You can definitely see the dropped positions (with you eyes alone, but use your iPhone's slowmo camera to confirm). You don't notice any line/line movement when moving fast, (because each animation frames typically cause movement further than a single line), but watch the end of the scrolling where it would normally be moving very slowly. Maybe if one's scroll speed is set to "really slow" it would look choppy. iOS (and Mac?) have many pixel based animations that have "snap points" - never being allowed to come to a rest in between.Īnd as far as eye candy goes, the scrolling looks awfully smooth to me as it is. You wouldn't be able to stop a scroll with e.g., only half the pixels of the top line showing.Ĭorrect. (Pixels aside, in general, animated navigation is super helpful because it lets you track blocks of code when scrolling up/down large amounts). But as it is, when it's slowing down, it jerks around a couple of times, which is jarring and makes it impossible to use that window of time to make sense of the content. There's real productivity wins as well, when the scroll view is slowing down with a proper pixel based easing function, you can make sense of some of the content before it reaches a complete stop (whether or not you use trackpad or keyboard driven animated scrolls). People would also use this via keyboard shortcuts (I would, and I do in other editors).Īnd then it would at best be purely eye candy At best, this would be for when scrolling using the mouse/trackpad
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |